From owner-svn-doc-head@freebsd.org Sun Jan 31 01:05:18 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A901BA73479; Sun, 31 Jan 2016 01:05:18 +0000 (UTC) (envelope-from wblock@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 467861211; Sun, 31 Jan 2016 01:05:18 +0000 (UTC) (envelope-from wblock@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u0V15HwE042221; Sun, 31 Jan 2016 01:05:17 GMT (envelope-from wblock@FreeBSD.org) Received: (from wblock@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u0V15Hog042220; Sun, 31 Jan 2016 01:05:17 GMT (envelope-from wblock@FreeBSD.org) Message-Id: <201601310105.u0V15Hog042220@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: wblock set sender to wblock@FreeBSD.org using -f From: Warren Block Date: Sun, 31 Jan 2016 01:05:17 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r48129 - head/en_US.ISO8859-1/htdocs/gnome X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Jan 2016 01:05:18 -0000 Author: wblock Date: Sun Jan 31 01:05:17 2016 New Revision: 48129 URL: https://svnweb.freebsd.org/changeset/doc/48129 Log: Whitespace-only fixes, translators please ignore. Modified: head/en_US.ISO8859-1/htdocs/gnome/news.xml Modified: head/en_US.ISO8859-1/htdocs/gnome/news.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/gnome/news.xml Sat Jan 30 22:54:51 2016 (r48128) +++ head/en_US.ISO8859-1/htdocs/gnome/news.xml Sun Jan 31 01:05:17 2016 (r48129) @@ -1,23 +1,23 @@ + News//EN" + "http://www.FreeBSD.org/XML/share/xml/news.dtd"> - $FreeBSD$ + $FreeBSD$ 2016 @@ -26,16 +26,18 @@ News//EN" January - 25 + 25 - - Announcing MATE 1.12 for FreeBSD! + + Announcing MATE 1.12 for FreeBSD! -

The FreeBSD GNOME team proudly presents MATE 1.12 for FreeBSD.

+

The FreeBSD GNOME team proudly presents MATE 1.12 for + FreeBSD.

-

This version of MATE uses the GTK+ 2 toolkit for stability, and has a number - of bugfixes for the applets.

-
+

This version of MATE uses the GTK+ 2 toolkit for + stability, and has a number of bugfixes for the + applets.

+
@@ -47,24 +49,25 @@ News//EN" August - 5 + 5 - - Announcing GNOME 3.16.2 for FreeBSD! + + Announcing GNOME 3.16.2 for FreeBSD! -

The FreeBSD GNOME team proudly presents GNOME 3.16 for FreeBSD.

+

The FreeBSD GNOME team proudly presents GNOME 3.16 for + FreeBSD.

-

The official GNOME 3.16 release notes can be found at - https://help.gnome.org/misc/release-notes/3.16/.

- -

This release was made possible by these people:

-

- Gustau Perez -
- Ting-Wei_Lan -
-

-
+

The official GNOME 3.16 release notes can be found at + https://help.gnome.org/misc/release-notes/3.16/.

+ +

This release was made possible by these people:

+

+ Gustau Perez +
+ Ting-Wei_Lan +
+

+
@@ -72,23 +75,27 @@ News//EN" July - 27 + 27 - - Announcing MATE 1.10.0 for FreeBSD! + + Announcing MATE 1.10.0 for FreeBSD! -

Presenting the MATE 1.10.0 Desktop Environment for FreeBSD. - The official release notes for this release can be found at - http://mate-desktop.org/blog/2015-06-11-mate-1-10-released/

+

Presenting the MATE 1.10.0 Desktop Environment for + FreeBSD. The official release notes for this release can + be found at + http://mate-desktop.org/blog/2015-06-11-mate-1-10-released/

-

This version of MATE is still built on the GTK+ 2 toolkit.

+

This version of MATE is still built on the GTK+ 2 + toolkit.

-

Replace mate-dialogs with zenity and mate-calc with galculator.

+

Replace mate-dialogs with zenity and mate-calc with + galculator.

-

Thanks go to Gustau Perez for helping track MATE development.

-
+

Thanks go to Gustau Perez for helping track MATE + development.

+
- + @@ -98,47 +105,48 @@ News//EN" November - 19 + 19 - - Announcing GNOME 2.32.1 for FreeBSD! + + Announcing GNOME 2.32.1 for FreeBSD! -

Presenting GNOME 2.32.1 for FreeBSD. The official release - notes for this release can be found at - - http://library.gnome.org/misc/release-notes/2.32/

- -

This will be the last release of the GNOME 2.x series, mainly a bugfix - and bridge release to the first release of the GNOME 3.x series.

- -

This release features commits by avl, marcus, mezz and myself.

- -

The FreeBSD GNOME Team would like to thank the following contributors - and testers for there help with this release:

- -

- Zane C.B. -
- romain@ -
- Olaf Seibert -
- DomiX -
- Bapt -
- jsa@ -
- miwi@ -
- Sergio de Almeida Lenzi -
- Maxim Samsonov -
- Kris Moore -
-

-
+

Presenting GNOME 2.32.1 for FreeBSD. The official release + notes for this release can be found at + http://library.gnome.org/misc/release-notes/2.32/

+ +

This will be the last release of the GNOME 2.x series, + mainly a bugfix and bridge release to the first release of + the GNOME 3.x series.

+ +

This release features commits by avl, marcus, mezz and + myself.

+ +

The FreeBSD GNOME Team would like to thank the following + contributors and testers for there help with this + release:

+ +

+ Zane C.B. +
+ romain@ +
+ Olaf Seibert +
+ DomiX +
+ Bapt +
+ jsa@ +
+ miwi@ +
+ Sergio de Almeida Lenzi +
+ Maxim Samsonov +
+ Kris Moore +

+
@@ -146,168 +154,167 @@ News//EN" May - 10 + 10 - - Announcing GNOME 2.30.1. for FreeBSD! + + Announcing GNOME 2.30.1. for FreeBSD! -

Presenting GNOME 2.30.1 for FreeBSD. The official release - notes for this release can be found at - - http://library.gnome.org/misc/release-notes/2.30/

+

Presenting GNOME 2.30.1 for FreeBSD. The official release + notes for this release can be found at + http://library.gnome.org/misc/release-notes/2.30/

-

This release brings initial PackageKit support, Upower (replaces - power management part of hal), cuse4bsd integration with HAL and cheese, - and a faster Evolution.

+

This release brings initial PackageKit support, Upower + (replaces power management part of hal), cuse4bsd + integration with HAL and cheese, and a faster + Evolution.

-

Sadly GNOME 2.30.x will be the last release with FreeBSD 6.X support. - This will also be the last of the 2.x releases. The next release will - be the highly-anticipated GNOME 3.0 which will bring with it a new UI - experience.

+

Sadly GNOME 2.30.x will be the last release with FreeBSD + 6.X support. This will also be the last of the 2.x + releases. The next release will be the highly-anticipated + GNOME 3.0 which will bring with it a new UI + experience.

-

Currently, there are a few bugs with GNOME 2.30 that may be of note - for our users. Be sure to consult the 2.30 upgrade FAQ at - - http://www.freebsd.org/gnome/docs/faq230.html> - for specific upgrading instructions, and the up-to-date list of known - issues.

+

Currently, there are a few bugs with GNOME 2.30 that may + be of note for our users. Be sure to consult the 2.30 + upgrade FAQ at + http://www.freebsd.org/gnome/docs/faq230.html> + for specific upgrading instructions, and the up-to-date + list of known issues.

-

This release features commits by: avl, ahze, bland, marcus, mezz - and myself.

+

This release features commits by: avl, ahze, bland, + marcus, mezz and myself.

-

The FreeBSD GNOME Team would like to thank Anders F Bjorklund for - doing the initial packagekit porting.

+

The FreeBSD GNOME Team would like to thank Anders F + Bjorklund for doing the initial packagekit porting.

-

And the following contributors and testers for there help with this - release:

+

And the following contributors and testers for there help + with this release:

-

- Eric L. Chen -
+

+ Eric L. Chen +
- Vladimir Grebenschikov -
+ Vladimir Grebenschikov +
- Sergio de Almeida Lenzi -
+ Sergio de Almeida Lenzi +
- DomiX -
+ DomiX +
- walder -
+ walder +
- crsd -
+ crsd +
- Kevin Oberman -
+ Kevin Oberman +
- Michal Varga -
+ Michal Varga +
- Pavel Plesov -
+ Pavel Plesov +
- Bapt -
+ Bapt +
- kevin -
+ kevin +
- and Ion-Mihai Tetcu for running two exp-runs for us. -
-

-
+ and Ion-Mihai Tetcu for running two exp-runs for us. +

+
- + 2009 November - 28 + 28 - - Announcing GNOME 2.28.1. for FreeBSD! + + Announcing GNOME 2.28.1. for FreeBSD! -

Presenting GNOME 2.28.1 for FreeBSD. The official release - notes for this release can be found at - - http://library.gnome.org/misc/release-notes/2.28/ +

Presenting GNOME 2.28.1 for FreeBSD. The official release + notes for this release can be found at + http://library.gnome.org/misc/release-notes/2.28/. + Officially, this is mostly a polishing release in + preparation for GNOME 3.0 due in about a year.

- . Officially, this is mostly a polishing release in preparation - for GNOME 3.0 due in about a year.

+

On the FreeBSD front, though, a lot went into this + release. Major thanks goes to kwm and avl who did a lot + of the porting work for this release. In particular, kwm + brought in Evolution MAPI support for better Microsoft + Exchange integration. Avl made sure that the new gobject + introspection repository ports were nicely + compartmentalized so that large dependencies aren't + brought in wholesale.

-

On the FreeBSD front, though, a lot went into this release. - Major thanks goes to kwm and avl who did a lot of the porting - work for this release. In particular, kwm brought in Evolution - MAPI support for better Microsoft Exchange integration. Avl - made sure that the new gobject introspection repository ports - were nicely compartmentalized so that large dependencies aren't - brought in wholesale.

+

But, every GNOME team member (ahze, avl, bland, kwm, + mezz, and myself) contributed to this release.

-

But, every GNOME team member (ahze, avl, bland, kwm, mezz, - and myself) contributed to this release.

+

Other major improvements include an updated HAL with + better volume probing code, ufsid integration, and support + for volume names containing spaces (big thanks to J.R. + Oldroyd); a new WebKit; updated AbiWord; an updated Gimp; + and a preview of the new GNOME Shell project (thanks to + Pawel Worach).

-

Other major improvements include an updated HAL with better - volume probing code, ufsid integration, and support for volume - names containing spaces (big thanks to J.R. Oldroyd); a new - WebKit; updated AbiWord; an updated Gimp; and a preview of the - new GNOME Shell project (thanks to Pawel Worach).

+

The FreeBSD GNOME Team would like to that the following + additional contributors to this release whose patches and + testing really helped make it a success:

-

The FreeBSD GNOME Team would like to that the following - additional contributors to this release whose patches and - testing really helped make it a success:

+

+ Andrius Morkunas +
-

- Andrius Morkunas -
+ Dominique Goncalves +
- Dominique Goncalves -
+ Eric L. Chen +
- Eric L. Chen -
+ J.R. Oldroyd +
- J.R. Oldroyd -
+ Joseph S. Atkinson +
- Joseph S. Atkinson -
+ Li +
- Li -
+ Pawel Worach +
- Pawel Worach -
+ Romain Tarti?re +
- Romain Tarti?re -
+ Thomas Vogt +
- Thomas Vogt -
+ Yasuda Keisuke +
- Yasuda Keisuke -
+ Rui Paulo +
- Rui Paulo -
+ Martin Wilke +
- Martin Wilke -
+ (and an extra shout out to miwi and pav for the pointyhat + runs)

- (and an extra shout out to miwi and pav for the pointyhat runs) -
-

- -

We would like to send this release out to Alexander Loginov - (avl) in hopes that he feels better soon.

-
+

We would like to send this release out to Alexander + Loginov (avl) in hopes that he feels better soon.

+
@@ -315,30 +322,30 @@ News//EN" April - 10 + 10 - - Announcing GNOME 2.26.0 for FreeBSD! + + Announcing GNOME 2.26.0 for FreeBSD! -

The FreeBSD GNOME team is proud to announce the release of - GNOME 2.26.0 for FreeBSD. The official release notes can be - found at - - http://library.gnome.org/misc/release-notes/2.26/ - - . On the FreeBSD front, we introduced a port of libxul 1.9 as - an alternative for Firefox 2.0 as a Gecko provider. Almost - all of the Gecko consumers can make use of this provider by - setting: -
- - WITH_GECKO=libxul -
- - The GNOME 2.26 port was done by ahze, kwm, marcus, and mezz - with contributions by Joseph S. Atkinson, Peter Wemm, Eric L. - Chen, Martin Matuska, Craig Butler, and Pawel Worach.

-
+

The FreeBSD GNOME team is proud to announce the release + of GNOME 2.26.0 for FreeBSD. The official release notes + can be found at + http://library.gnome.org/misc/release-notes/2.26/. + + On the FreeBSD front, we introduced a port of libxul 1.9 + as an alternative for Firefox 2.0 as a Gecko provider. + Almost all of the Gecko consumers can make use of this + provider by setting: +
+ + WITH_GECKO=libxul +
+ + The GNOME 2.26 port was done by ahze, kwm, marcus, and + mezz with contributions by Joseph S. Atkinson, Peter Wemm, + Eric L. Chen, Martin Matuska, Craig Butler, and Pawel + Worach.

+
@@ -346,30 +353,30 @@ News//EN" January - 9 + 9 - - Announcing GNOME 2.24.2 for FreeBSD! + + Announcing GNOME 2.24.2 for FreeBSD! -

The FreeBSD GNOME team is proud to announce the release of - GNOME 2.24.2 for FreeBSD. The official release notes can be - found at - - http://library.gnome.org/misc/release-notes/2.24/ - - . On the FreeBSD front, this release introduces Fuse support - in HAL, adds multi-CPU support to libgtop, WebKit updates, - and fixes some long-standing seahorse and gnome-keyring - bugs.

- -

This release features commits by adamw, ahze, kwm, mezz, - and myself. It would not have been possible without are - contributors and testers: Alexander Loginov, Craig Butler, - Dmitry Marakasov, Eric L. Chen, Joseph S. Atkinson, Kris - Moore, Lapo Luchini, Nikos Ntarmos, Pawel Worach, Romain - Tartiere, TAOKA Fumiyoshi, Romain Tartiere, Yasuda Keisuke, - Zyl aZ, bf, Florent Thoumie, Peter Wemm, and pluknet.

-
+

The FreeBSD GNOME team is proud to announce the release + of GNOME 2.24.2 for FreeBSD. The official release notes + can be found at + http://library.gnome.org/misc/release-notes/2.24/. + + On the FreeBSD front, this release introduces Fuse support + in HAL, adds multi-CPU support to libgtop, WebKit updates, + and fixes some long-standing seahorse and gnome-keyring + bugs.

+ +

This release features commits by adamw, ahze, kwm, mezz, + and myself. It would not have been possible without are + contributors and testers: Alexander Loginov, Craig Butler, + Dmitry Marakasov, Eric L. Chen, Joseph S. Atkinson, Kris + Moore, Lapo Luchini, Nikos Ntarmos, Pawel Worach, Romain + Tartiere, TAOKA Fumiyoshi, Romain Tartiere, Yasuda + Keisuke, Zyl aZ, bf, Florent Thoumie, Peter Wemm, and + pluknet.

+
@@ -381,30 +388,30 @@ News//EN" March - 24 + 24 - - Announcing GNOME 2.22.0 for FreeBSD! + + Announcing GNOME 2.22.0 for FreeBSD! -

The FreeBSD GNOME team is proud to announce the release of - GNOME 2.22.0 for FreeBSD. The official GNOME 2.22 release - notes can be found at - - http://library.gnome.org/misc/release-notes/2.22/ - - . On the FreeBSD front, this release features an updated hal - port with support for video4linux devices, DRM (Direct - Rendering), and better support of removable media. Work is - also underway to tie webkit more closely into GNOME. As part - of the GNOME 2.22 upgrade, GStreamer received a rather large - upgrade as well. Be sure to consult UPDATING on the proper - steps to upgrade all of your GNOME ports.

- -

This release would not have been possible without the - contributions and testing efforts of the following people: - Pawel Worach, kan, edwin, Peter Ulrich Kruppa, J. W. - Ballantine, Yasuda Keisuke, and Andriy Gapon.

-
+

The FreeBSD GNOME team is proud to announce the release + of GNOME 2.22.0 for FreeBSD. The official GNOME 2.22 + release notes can be found at + http://library.gnome.org/misc/release-notes/2.22/. + + On the FreeBSD front, this release features an updated hal + port with support for video4linux devices, DRM (Direct + Rendering), and better support of removable media. Work + is also underway to tie webkit more closely into GNOME. As + part of the GNOME 2.22 upgrade, GStreamer received a + rather large upgrade as well. Be sure to consult UPDATING + on the proper steps to upgrade all of your GNOME + ports.

+ +

This release would not have been possible without the + contributions and testing efforts of the following people: + Pawel Worach, kan, edwin, Peter Ulrich Kruppa, J. W. + Ballantine, Yasuda Keisuke, and Andriy Gapon.

+
@@ -416,78 +423,78 @@ News//EN" October - 24 - - - Announcing GNOME 2.20.1 for FreeBSD! + 24 -

Presenting GNOME 2.20.1 and all related works for FreeBSD. - The official GNOME 2.20 release notes can be found at - - http://www.gnome.org/start/2.20/notes/en/ + + Announcing GNOME 2.20.1 for FreeBSD! - . Beyond that, this update includes the new GIMP 2.4 - (courtesy of ahze).

+

Presenting GNOME 2.20.1 and all related works for + FreeBSD. The official GNOME 2.20 release notes can be + found at + http://www.gnome.org/start/2.20/notes/en/. + Beyond that, this update includes the new GIMP 2.4 + (courtesy of ahze).

-

The GNOME 2.20 update also includes a huge change in the - FreeBSD GNOME hierarchy. We are now using the more standard - DATADIR of ${PREFIX}/share rather than ${PREFIX}/share/gnome. - The result is that fewer patches and hacks are needed to port - GNOME components to FreeBSD. This will mean some user changes - may be required, so be sure to read /usr/ports/UPDATING for - more details.

+

The GNOME 2.20 update also includes a huge change in the + FreeBSD GNOME hierarchy. We are now using the more + standard DATADIR of ${PREFIX}/share rather than + ${PREFIX}/share/gnome. The result is that fewer patches + and hacks are needed to port GNOME components to FreeBSD. + This will mean some user changes may be required, so be + sure to read /usr/ports/UPDATING for more details.

-

This release and the things we accomplished in it would - not have been possible without mezz's crazy idea to collapse - DATADIR, and his persistence to make it happen successfully. - Ahze and pav also deserve thanks for their work on porting - modules and testing the whole ball of wax on pointyhat - (respectively).

+

This release and the things we accomplished in it would + not have been possible without mezz's crazy idea to + collapse DATADIR, and his persistence to make it happen + successfully. Ahze and pav also deserve thanks for their + work on porting modules and testing the whole ball of wax + on pointyhat (respectively).

-

The FreeBSD GNOME team would also like to thank our - various testers and contributors:

+

The FreeBSD GNOME team would also like to thank our + various testers and contributors:

-

Yasuda Keisuke -
+

+ Yasuda Keisuke +
- Frank Jahnke -
+ Frank Jahnke +
- Pawel Worach -
+ Pawel Worach +
- Brian Gruber -
+ Brian Gruber +
- Franz Klammer -
+ Franz Klammer +
- Yuri Pankov -
+ Yuri Pankov +
- Nick Barkas -
+ Nick Barkas +
- Cristian KLEIN -
+ Cristian KLEIN +
- Tony Maher -
+ Tony Maher +
- Scot Hetzel -
+ Scot Hetzel +
- Martin Matuska (mm) -
+ Martin Matuska (mm) +
- Benoit Dejean -
+ Benoit Dejean +
- Martin Wilke (miwi) -
+ Martin Wilke (miwi) +
- (And anyone else I may have missed)

-
+ (And anyone else I may have missed)

+
@@ -495,30 +502,23 @@ News//EN" August - 4 + 4 - - GNOME 2.19.6 available for FreeBSD + + GNOME 2.19.6 available for FreeBSD -

Okay, okay, I have missed a few updates. But the FreeBSD - GNOME team has not been slacking. We've been keeping up with - the latest GNOME development releases including this - - latest one - - . Checkout the ports and - packages - - to see where GNOME 2.20 currently stands. Since 2.10 Beta 1 - is right around the corner, now is also the time to start - putting together some killer FreeBSD GNOME screenshots. Send - all submissions to - - freebsd-gnome@FreeBSD.org - - .

-
+

Okay, okay, I have missed a few updates. But the FreeBSD + GNOME team has not been slacking. We've been keeping up + with the latest GNOME development releases including this + latest one. + Check out the ports and + packages + to see where GNOME 2.20 currently stands. Since 2.10 Beta + 1 is right around the corner, now is also the time to + start putting together some killer FreeBSD GNOME + screenshots. Send all submissions to + freebsd-gnome@FreeBSD.org.

+
@@ -526,24 +526,22 @@ News//EN" June - 9 + 9 - - GNOME 2.19.3 available for FreeBSD + + GNOME 2.19.3 available for FreeBSD -

The third release on the path to GNOME 2.20 is now - available in both port and - package - - forms. There is one known build issue with - gnome-system-monitor and FreeBSD < 7-CURRENT that we hope - to have worked out soon. Along with this release comes the - GNOME 2.20 (and beyond!) - roadmap - - . This will prepare you for the exciting new features in - store for our favorite Desktop Environment.

-
+

The third release on the path to GNOME 2.20 is now + available in both port and + package + forms. There is one known build issue with + gnome-system-monitor and FreeBSD < 7-CURRENT that we + hope to have worked out soon. Along with this release + comes the GNOME 2.20 (and beyond!) + roadmap. + This will prepare you for the exciting new features in + store for our favorite Desktop Environment.

+
@@ -551,52 +549,45 @@ News//EN" May - 31 - - - GNOME 2.18.2 available for FreeBSD + 31 -

The next bug fix release for GNOME 2.18 has been - - released + + GNOME 2.18.2 available for FreeBSD - and ports and - packages - - are available for FreeBSD. So the only question is, why - haven't you upgraded yet?

-
+

The next bug fix release for GNOME 2.18 has been + released + and ports and + packages + are available for FreeBSD. So the only question is, why + haven't you upgraded yet?

+
- 6 - - - GNOME 2.19.1 available for FreeBSD - -

GNOME forges ahead with the first release in the - development train that will become GNOME 2.20. As always, - FreeBSD is right there with them. Only we bring a twist. This - time around, we are doing yet another bit of housekeeping, - and dropping the "share/gnome" DATADIR. This means that the - FreeBSD GNOME installation will be more like all the other - GNOME distributions. The net gain is that porting new GNOME - applications to FreeBSD should be much easier with fewer - hacks and patches.

- -

At this point, the - MarcusCom - tree - - is safe to use for most ports. There is still quite a few - ports that still require conversion, and we will be working - on those in the weeks to come. In particular, the Desktop and - all gnome2 meta-ports are safe; and - Packages - - are available for the GNOME Desktop.

-
+ 6 + + + GNOME 2.19.1 available for FreeBSD + +

GNOME forges ahead with the first release in the + development train that will become GNOME 2.20. As always, + FreeBSD is right there with them. Only we bring a twist. + This time around, we are doing yet another bit of + housekeeping, and dropping the "share/gnome" DATADIR. + This means that the FreeBSD GNOME installation will be + more like all the other GNOME distributions. The net gain + is that porting new GNOME applications to FreeBSD should + be much easier with fewer hacks and patches.

+ +

At this point, the + MarcusCom tree + is safe to use for most ports. There is still quite a few + ports that still require conversion, and we will be + working on those in the weeks to come. In particular, the + Desktop and all gnome2 meta-ports are safe; and + Packages + are available for the GNOME Desktop.

+
@@ -604,27 +595,21 @@ News//EN" April - 11 + 11 - - GNOME 2.18.1 available for FreeBSD + + GNOME 2.18.1 available for FreeBSD -

GNOME 2.18.1 has been - - released - - and ports and - packages - - are available for everyone's favorite operating system. This - release is a polishing of 2.18.0, so expect a more stable, - nicer looking desktop experience. On top of that, some of our - users have also submitted - screenshots - *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-head@freebsd.org Sun Jan 31 15:36:45 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 33FB8A7437B; Sun, 31 Jan 2016 15:36:45 +0000 (UTC) (envelope-from wblock@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 018FCF3B; Sun, 31 Jan 2016 15:36:44 +0000 (UTC) (envelope-from wblock@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u0VFahoq001526; Sun, 31 Jan 2016 15:36:43 GMT (envelope-from wblock@FreeBSD.org) Received: (from wblock@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u0VFahlj001525; Sun, 31 Jan 2016 15:36:43 GMT (envelope-from wblock@FreeBSD.org) Message-Id: <201601311536.u0VFahlj001525@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: wblock set sender to wblock@FreeBSD.org using -f From: Warren Block Date: Sun, 31 Jan 2016 15:36:43 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r48130 - head/en_US.ISO8859-1/htdocs X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Jan 2016 15:36:45 -0000 Author: wblock Date: Sun Jan 31 15:36:43 2016 New Revision: 48130 URL: https://svnweb.freebsd.org/changeset/doc/48130 Log: "Serial commas are only necessary when you want to be correct." Modified: head/en_US.ISO8859-1/htdocs/index.xsl Modified: head/en_US.ISO8859-1/htdocs/index.xsl ============================================================================== --- head/en_US.ISO8859-1/htdocs/index.xsl Sun Jan 31 01:05:17 2016 (r48129) +++ head/en_US.ISO8859-1/htdocs/index.xsl Sun Jan 31 15:36:43 2016 (r48130) @@ -39,7 +39,7 @@

&os; is an advanced computer operating system used to power - modern servers, desktops and + modern servers, desktops, and embedded platforms. A large @@ -47,7 +47,7 @@ href="&base;/doc/en_US.ISO8859-1/articles/contributors/staff-committers.html">community has continually developed it for more than thirty years. Its advanced - networking, security and storage + networking, security, and storage features have made &os; the platform of choice for many of the busiest web sites From owner-svn-doc-head@freebsd.org Sun Jan 31 16:30:19 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E56D6A73503; Sun, 31 Jan 2016 16:30:19 +0000 (UTC) (envelope-from bjk@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9F675901; Sun, 31 Jan 2016 16:30:19 +0000 (UTC) (envelope-from bjk@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u0VGUI19016229; Sun, 31 Jan 2016 16:30:18 GMT (envelope-from bjk@FreeBSD.org) Received: (from bjk@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u0VGUIwK016228; Sun, 31 Jan 2016 16:30:18 GMT (envelope-from bjk@FreeBSD.org) Message-Id: <201601311630.u0VGUIwK016228@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bjk set sender to bjk@FreeBSD.org using -f From: Benjamin Kaduk Date: Sun, 31 Jan 2016 16:30:18 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r48131 - head/en_US.ISO8859-1/htdocs/news/status X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Jan 2016 16:30:20 -0000 Author: bjk Date: Sun Jan 31 16:30:18 2016 New Revision: 48131 URL: https://svnweb.freebsd.org/changeset/doc/48131 Log: Add GNOME entry from kwm Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Sun Jan 31 15:36:43 2016 (r48130) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Sun Jan 31 16:30:18 2016 (r48131) @@ -4391,4 +4391,46 @@ SoldierX + + + GNOME on &os; + + + + &os; GNOME Team + freebsd-gnome@FreeBSD.org + + + + + &os; Gnome Website + Devel Repository + Upstream Build Bot + USE_GNOME Porter's Handbook Chapter + + + +

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, due to limited available time there was not + much progress. This began to change in December, when work + started on porting MATE 1.12 and CINNAMON 2.8 to &os;.

+ + + + +

The &os; GNOME website is stale. Work is under way to + improve it.

+
+ + +

Continue working on investigating the issues blocking + GNOME 3.18.

+
+
+ From owner-svn-doc-head@freebsd.org Sun Jan 31 21:51:41 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A2B7DA749C5; Sun, 31 Jan 2016 21:51:41 +0000 (UTC) (envelope-from wblock@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6EC26B4E; Sun, 31 Jan 2016 21:51:41 +0000 (UTC) (envelope-from wblock@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u0VLpe9E013448; Sun, 31 Jan 2016 21:51:40 GMT (envelope-from wblock@FreeBSD.org) Received: (from wblock@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u0VLpeKR013447; Sun, 31 Jan 2016 21:51:40 GMT (envelope-from wblock@FreeBSD.org) Message-Id: <201601312151.u0VLpeKR013447@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: wblock set sender to wblock@FreeBSD.org using -f From: Warren Block Date: Sun, 31 Jan 2016 21:51:40 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r48132 - head/en_US.ISO8859-1/htdocs/news/status X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Jan 2016 21:51:41 -0000 Author: wblock Date: Sun Jan 31 21:51:40 2016 New Revision: 48132 URL: https://svnweb.freebsd.org/changeset/doc/48132 Log: Editing pass. Yes, I changed stuff. It got a bit weird with the time travel in the third act, and the whole car chase scene did not make sense. Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Sun Jan 31 16:30:18 2016 (r48131) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Sun Jan 31 21:51:40 2016 (r48132) @@ -104,7 +104,7 @@

LKL ("Linux Kernel as a Library") is a special "architecture" of the full Linux kernel that builds as a userspace library on various platforms, including &os;. One - application of such a library is using Linux's filesystem drivers + application of such a library is using Linux filesystem drivers to implement a FUSE backend.

fusefs-lkl's lklfuse binary is such a FUSE @@ -112,14 +112,14 @@ BTRFS read-write, using the native drivers from Linux.

-

The sysutils/fusefs-lkl port may now be installed from +

sysutils/fusefs-lkl can now be installed either from packages or ports, providing access to these filesystems on &os; via FUSE.

- Style(9) enhanced to allow C99 'bool' + <tt>style(9)</tt> Enhanced to Allow C99 <tt>bool</tt> @@ -146,7 +146,7 @@

Use of bool is now allowed. It was allowed - previously, as well, but now it's really allowed. Party + previously, as well, but now it is really allowed. Party like it's 1999!

@@ -167,7 +167,7 @@
- Sysctl enhancements + <tt>sysctl</tt> Enhancements @@ -201,13 +201,13 @@ -

This quarter, support was added for fixed-width sysctls +

Support was added for fixed-width sysctls (signed and unsigned 8-bit, 16-bit, 32-bit, and 64-bit integers). The new KPIs are documented in the sysctl(9) manual page. The sysctl(8) command line tool supports all of the new types.

-

sysctl(8) gained the '-t' flag, which prints sysctl type +

sysctl(8) gained the -t flag, which prints sysctl type information (the original patch was submitted by Yoshihiro Ota). This support includes the newly added fixed-width types.

@@ -218,7 +218,7 @@
- ioat(4) driver enhancements + <tt>ioat(4)</tt> Driver Enhancements @@ -240,8 +240,8 @@ engines built into some Intel Server/Storage platform CPUs.

-

This quarter, several enhancements were made to the driver. - The driver now avoids memory allocation in locked paths, which +

Several enhancements were made to the driver. + It now avoids memory allocation in locked paths, which should avoid deadlocking in memory pressure scenarios. Support for Broadwell-EP devices has been added. The "blockfill" operation and a non-contiguous 8 KB copy @@ -261,7 +261,7 @@ - ntb_hw(4)/if_ntb(4) driver synced up to Linux + <tt>ntb_hw(4)</tt>/<tt>if_ntb(4)</tt> Driver Synced up to Linux @@ -311,7 +311,7 @@ - &os; on newer ARM boards + &os; on Newer ARM Boards @@ -337,9 +337,9 @@ -

This quarter, we made the changes necessary to support the +

We made the changes required to support the Amlogic Meson Ethernet controller on the Hardkernel ODROID-C1 - board which has an Amlogic aml8726-m8b SoC. The main effort + board, which has an Amlogic aml8726-m8b SoC. The main effort needed was to write a glue driver for the Ethernet controller — the Amlogic Meson Ethernet controller is compatible with Synopsys DesignWare 10/100/1000 Ethernet MAC @@ -387,7 +387,7 @@ - "FreeBSD Mastery: Specialty Filesystems" early access version now available + "FreeBSD Mastery: Specialty Filesystems" Early Access Version Now Available @@ -413,7 +413,7 @@ NFSv4 ACLs, iSCSI, CIFS, and more.

If you act really quickly, you can get the electronic early - access version at a 10% discount. You'll get the final ebook when + access version at a 10% discount. You will get the final ebook when it comes out as well. (This offer evaporates when the final version comes out.)

@@ -437,10 +437,10 @@ -

The KGDB option is now on by default in the devel/gdb +

The KGDB option is now on by default in the devel/gdb port.

-

The changes to support cross-debugging of crashdumps in +

Changes to support cross-debugging of crashdumps in libkvm were committed to HEAD in r291406.

A new thread target for &os; that is suitable for merging @@ -479,7 +479,7 @@ - iMX.6 video output support + iMX.6 Video Output Support @@ -521,7 +521,7 @@ - Touchscreen support for Raspberry Pi and Beaglebone Black + Touchscreen Support for Raspberry Pi and Beaglebone Black @@ -614,7 +614,7 @@ vnodes.

Vnode cache recycling was reworked to meet free and unused - vnodes targets. Free vnodes are rarely completely free; rather, + vnode targets. Free vnodes are rarely completely free; rather, they are just ones that are cheap to recycle. Usually they are for files which have been stat'd but not read; these usually have inode and namecache data attached to them. The free vnode target @@ -631,18 +631,18 @@ recycling from the free list and normal use maintains this state. Sometimes the free list is below vlowat or even empty, but this state is even better for immediate use, provided the cache is not - full. Otherwise, vnlru_proc() runs to reclaim enough vnodes + full. Otherwise, vnlru_proc() runs to reclaim enough vnodes (usually non-free ones) to reach one of these states. The watermarks are currently hard-coded as 4% and 9% of the available space. These, and the default of 25% for wantfreevnodes, are too - large if the memory size is large. E.g., 9% of 75% of MAXVNODES - is more than 566000 vnodes to reclaim whenever vnlru_proc() + large if the memory size is large. For example, 9% of 75% of MAXVNODES + is more than 566000 vnodes to reclaim whenever vnlru_proc() becomes active.

The vfs.vlru_alloc_cache_src sysctl is removed. New code frees namecache sources as the last chance to satisfy the highest watermark, instead of selecting source vnodes randomly. - This provides good enough behaviour to keep vn_fullpath() working + This provides good enough behavior to keep vn_fullpath() working in most situations. Filesystem layouts with deep trees, where the removed knob was required, is thus handled automatically.

@@ -661,14 +661,14 @@ times at system startup, and then only rarely again. The frees are done only if the vnode zone shrinks, which never happens in practice. For those curious about the avoided work, look at the - vnode_init() and vnode_fini() functions in sys/kern/vfs_subr.c to + vnode_init() and vnode_fini() functions in sys/kern/vfs_subr.c to see the code that has been removed from the main vnode allocation/free path.

- Improvements to QLogic HBA driver + Improvements to the QLogic HBA Driver @@ -681,8 +681,8 @@ -

The QLogic HBA driver isp(4) received a - substantial set of changes. Their primary goal was to make Fibre +

The QLogic HBA driver, isp(4), received a + substantial set of changes. The primary goal was to make the Fibre Channel target role work well with CTL, but many other things were also fixed/improved:

@@ -727,7 +727,7 @@
- Raspberry Pi: VideoCore userland application packaging + Raspberry Pi: VideoCore Userland Application Packaging @@ -757,7 +757,7 @@ misc/raspberrypi-userland for them. He also created a port for omxplayer (a low-level video player that utilizes VideoCore APIs) and is working on a port for Kodi - (ex-XBMC), a more user-firendly media player software with + (formerly XBMC), a more user-firendly media player software with Raspberry Pi support.

@@ -786,15 +786,15 @@ It is the product of the merge between the LXDE-Qt and the Razor-qt projects.

-

The porting effort remains heavily a work in progress: it - needs some components of Plasma 5 (the new major KDE's - workspace).

+

The porting effort remains very much a work in progress: it + needs some components of Plasma 5, the new major KDE + workspace.

Currently, only the 0.10 branch is functional. See our wiki page for a complete list of applications.

-

We also sent updates for some components of LXDE (required - for the LXQt desktop):

+

We also sent updates for some components of LXDE, required + for the LXQt desktop:

  • x11/menu-cache 1.0.1
  • @@ -851,9 +851,9 @@ new ports, in particular:

      -
    • Socket.IO (a library for realtime web applications)
    • +
    • Socket.IO, a library for realtime web applications
    • -
    • Jison (a JavaSript parser generator)
    • +
    • Jison, a JavaSript parser generator

    We have improved the USES framework:

    @@ -865,8 +865,8 @@
  • node-gyp is now well-integrated into the USES framework, via the build argument.
  • -
  • The pkg-plist is now automatically generated, - in order to make the portlint utility happy.
  • +
  • The pkg-plist is now automatically generated + to make portlint happy.

Each port is up-to-date.

@@ -923,7 +923,7 @@ -

Propose a patch to upstreamto fix Xfdashboard with our +

Propose a patch to upstream to fix Xfdashboard with our version of OpenGL (it currently coredumps).

@@ -950,7 +950,7 @@

I recently became involved with &os; (as in, the last 2-3 weeks), and found myself quickly involved with Ports development. - What quickly struck me was the difficulty in providing a Python + What struck me immediately was the difficulty in providing a Python package that was depended upon by multiple versions of Python. As it turns out, poudriere can currently only generate one package per port, meaning that a Python version-neutral (compatible with @@ -959,7 +959,7 @@

I discussed the issue with &a.koobs;, who suggested that I look into implementing a "variants protocol" within the - Ports framework and the necessary changes to poudriere in order to + Ports framework and the necessary changes to poudriere to allow a port to generate more than one package.

Support for variants is strongly needed in Ports and @@ -994,8 +994,8 @@ in my heels and have implemented a proof-of-concept implementation of variants in the Ports framework, including the necessary modifications to poudriere in order to support it. It was mildly - upsetting to find that poudriere is mostly written in Bourne shell - scripts, but press on I did nonetheless.

+ upsettling to find that poudriere is mostly written in Bourne shell + scripts, but I pressed on nonetheless.

I started with the @@ -1007,7 +1007,7 @@ changes.

This is a work in progress, and I would - love to hear your feedback. I've enjoyed my first few weeks + love to hear your feedback. I have enjoyed my first few weeks working on &os;, and I hope to stay here for quite some time.

@@ -1025,7 +1025,7 @@ - New tools to enhance the porting experience + New Tools to Enhance the Porting Experience @@ -1047,10 +1047,10 @@

When I starting working on ports for &os; in the last couple of weeks, I found that my workflow was not as efficient as - it could be, using just the available tools, so I made a few that + it could be using just the available tools, so I made a few that could be useful to the development community at large. All of - these have been added to the Ports tree, or otherwise will soon be - added, so you can play with them today!

+ these have been or will soon be added to the Ports tree, + so you can play with them today!

pytoport is a command-line application that generates a skeleton port for a given PyPI package name. It @@ -1073,27 +1073,27 @@ living in git and the larger upstream SVN tree I was using in poudriere. I built a tool called bandar that takes advantage of the FUSE version of unionfs to easily overlay my dev - tree on the upstream tree, run linting, poudriere and generate + tree on the upstream tree, run linting, poudriere, and generate archives with ease.

-

I'm very impressed with how easy it was to build more +

I am very impressed with how easy it was to build more tooling for &os;. I hope some of these tools will be of some use to you, and as always, I'd love to hear your feedback!

-

Improve skog to support searching a tree for a certain +

Improve skog to support searching a tree for a certain port.

-

Get the bandar port completed.

+

Get the bandar port completed.

-

Continue to improve pytoport, adding trove support and better - depedency handling.

+

Continue to improve pytoport, adding trove support and better + dependency handling.

@@ -1118,14 +1118,14 @@

The Out of Memory (OOM) code is intended to handle the situation where the system needs free memory to make progress, - while no memory can be reused. Most often, the situation is that + but no memory can be reused. Most often, the situation is that to free memory, the system needs more free memory. Consider a case where the system needs to page-out dirty pages, but needs to allocate structures to track the writes. OOM "solves" the problem by killing some selection of user processes. In other words, it trades away system deadlock by suffering a partial loss of user data. The assumption is that it is better to kill a - process and recover data in other processes, than lose + process and recover data in other processes than to lose everything.

Free memory in the &os; Virtual Memory (VM) system appears @@ -1133,16 +1133,16 @@ by a process, for example unmapping private anonymous regions, or the last unlink of an otherwise unreferenced file with cached pages. Another source is the pagedaemon, which forcefully frees - pages which carry data, of course, after the data is moved to some + pages which carry data, of course after the data is moved to some other storage, like swap or file blocks. OOM is triggered when the pagedaemon definitely cannot free memory to satisfy the requests.

-

The old criteria to trigger OOM action was a combination of - low free swap space and a low count of free pages (the later is +

The old criteria to trigger the OOM action was a combination of + low free swap space and a low count of free pages (the latter is expressed precisely with the paging targets constants, but this is - not relevant to the discussion). That test is mostly incorrect, - e.g., a low free page state might be caused by a greedy consumer + not relevant to the discussion). That test is mostly incorrect. + For example, a low free page state might be caused by a greedy consumer allocating all pages freed by the page daemon in the current pass, but this does not preclude the page daemon from producing more pages. Also, since page-outs are asynchronous, the previous page @@ -1150,15 +1150,15 @@ they would appear some short time later.

More seriously, low swap space does not necessarily indicate - that we are in trouble: lots of pages may not require swap - allocations to freed, e.g., clean pages or pages backed by files. + that we are in trouble: lots of pages might not require swap + allocations to be freed, like clean pages or pages backed by files. The last notion is serious, since swap-less systems were considered as having full swap.

Instead of trying to deduce the deadlock from looking at the current VM state, the new OOM handler tracks the history of - page daemon passes. Only if several consequtive passes failed to - meet the paging target is an OOM kill considered neccessary. The + page daemon passes. Only when several consequtive passes failed to + meet the paging target is an OOM kill considered necessary. The count of consequent failed passes was selected empirically, by testing on small (32M) and large (512G) machines. Auto-tuning of the counter is possible, but requires some more architectural @@ -1169,15 +1169,15 @@ pages mapping entries (PTEs) installed into the machine paging structures. For different reasons, machine-dependent VM code (pmap) may remove the pte for a memory-resident page. Under some - circumstances, related to other measures to prevent low memory - deadlock, very large processes which consume all system memory, - could have few or no ptes, and the old OOM selector ignored the + circumstances related to other measures to prevent low memory + deadlock, very large processes which consume all system memory + could have few or no ptes. The old OOM selector ignored the process which caused the deadlock, killing unrelated processes.

-

A new function vm_pageout_oom_pagecount() was written which +

A new function, vm_pageout_oom_pagecount(), was written which applies a reasonable heuristic to estimate the number of pages - which would be freed by killing the given process. This + freed by killing the given process. This eliminates the effect of selecting small unrelated processes for OOM kill.

@@ -1205,7 +1205,7 @@ -

A new driver, cxgbei, that enables hardware +

A new driver, cxgbei, enabling hardware accelerated iSCSI with Chelsio's T5- and T4-based offload-capable cards, has been committed to HEAD. Both Initiator and Target are supported. The wire traffic is standard iSCSI (SCSI over TCP as @@ -1298,7 +1298,7 @@

Test the new release on different versions of &os;, Mac - OS X and Linux. In particular, testing on Mac OS X 10.9 (Mavericks) + OS X, and Linux. In particular, testing on Mac OS X 10.9 (Mavericks) and newer would be greatly appreciated.

@@ -1426,7 +1426,7 @@

GitLab is a web-based Git repository manager with many - features that is used by more than 100.000 organizations including + features that is used by more than 100,000 organizations including NASA and Alibaba. It also is a very long-standing entry on the "Wanted Ports" list of the &os; Wiki.

@@ -1437,9 +1437,9 @@ committed!

While the new version of GitLab 8.3 eases the porting, - there are big changes between the last working port of GitLab + there are big changes since the last working port of GitLab 7.14. Nonetheless, it could be expected to see the next working - port in the first quarter of 2016

+ port in the first quarter of 2016.

@@ -1484,12 +1484,12 @@ was regularly hit by missing IPv6 support when building ports.

I did some research into the impact of missing IPv6 support - on the ports tree. The results are that 10.308 of 25.522 ports - are not fetchable when using IPv6. This renders — through - dependencies — a total of 17.715 ports unbuildable from - IPv6-only systems. All you can do than is wait and hope that - distcache.FreeBSD.org caches the distfile. But this will take - some time, which may not be a luxury available when a piece of + on the ports tree. The results are that 10,308 of 25,522 ports + are not fetchable when using IPv6. This renders, through + dependencies, a total of 17,715 ports unbuildable from + IPv6-only systems. All you can do then is wait and hope that + distcache.FreeBSD.org caches the distfile. But this will take + some time, which might not be a luxury available when a piece of software in use is hit by a security issue.

Based on the research, a promotion campaign for IPv6 was @@ -1528,12 +1528,12 @@ are being worked on in our experimental repository.

As in previous quarters, we would like to thank several - people who have contributed with machines, patches and general + people who have contributed with machines, patches, and general help. Tobias Berner, &a.madpilot; (madpilot@), Adriaan de Groot, Ralf Nolden, &a.swills; (swills@), and &a.jpaetzel; (jpaetzel@) have been essential to our work.

-

The following big updates were landed in the ports tree +

The following big updates landed in the ports tree this quarter. In many cases, we have also contributed patches to the upstream projects.

@@ -1542,14 +1542,14 @@
  • Calligra 2.9.1, the latest release of the integrated work applications suite. Calligra had last been updated in the - ports tree in the end of 2013!
  • + ports tree at the end of 2013!
  • PyQt4 4.11.4, QScintilla2 2.9.1 and SIP 4.17.
  • PyQt5 5.5.1. Thanks to the work spearheaded by Guido Falsi and Tobias Berner in the previous quarter, the PyQt5 ports have finally been committed to the ports tree. Not only was this - long-awaited on its own, but it also allows other ports to be + long-awaited on its own, it allows other ports to be updated to their latest versions.
  • QtCreator 3.5.1 and 3.6.0.
  • @@ -1562,7 +1562,7 @@

    Work on updating the Qt5 ports to their latest version, as well as porting KDE Frameworks 5 and Plasma 5 to &os;, is well - underway in our experimental area51 repository. At the moment, it + under way in our experimental area51 repository. At the moment, it contains Qt5 5.5.1, KDE Frameworks 5.17.0, Plasma 5.5.1 and KDE Applications 15.12.0.

    @@ -1580,7 +1580,7 @@ -

    Land the KDE Frameworks 5 and Plasma 5 ports to the +

    Land the KDE Frameworks 5 and Plasma 5 ports in the tree.

    @@ -1626,7 +1626,7 @@ -

    As of the end of Q4 the ports tree holds a bit more +

    As of the end of the fourth quarter, the ports tree holds a bit more than 25,000 ports, and the PR count is around 2,000. The activity on the ports tree remains steady, with about 7,000 commits performed by almost 120 active @@ -1638,7 +1638,7 @@ reports were fixed, which makes an increase of about 20% compared to Q3.

    -

    In Q4 8 commit bits were taken in for safekeeping, +

    In Q4, eight commit bits were taken in for safekeeping, following an inactivity period of more than 18 months (lioux, lippe, simon, jhay, max, sumikawa, alexey, sperber). Three new developers were granted a ports commit bit (Kenji @@ -1647,7 +1647,7 @@

    Also related to the management of ports commit bits, nox's grants were revoked, since the &os; developers - learnt that Juergen Lock passed away.

    + learned that Juergen Lock had passed away.

    On the management side, no changes were made to the portmgr team during Q4.

    @@ -1656,9 +1656,9 @@ updates or cleanups. Amongst those noticeable changes are the update to GCC 4.9, CMake to 3.4.1, PostgreSQL to 9.4, and ruby-gems to 2.5.0. Some infrastructure changes included the - usage of a WRKSRC different from WRKDIR when NO_WRKSUBDIR - is set, the removal of bsd.cpu.mk from sys.mk, and the - move of QT_NONSTANDARD to bsd.qt.mk.

    + usage of a WRKSRC different from WRKDIR when NO_WRKSUBDIR + is set, the removal of bsd.cpu.mk from sys.mk, and the + move of QT_NONSTANDARD to bsd.qt.mk.

    @@ -1706,14 +1706,14 @@ -

    This quarter, the bugmeister team has gained a new member, +

    The bugmeister team has gained a new member, Mahdi Mokhtari (mokhi64@gmail.com). Mahdi has been contributing to the &os; Project for just over one month. After getting started by creating ports for Chef-Server and MySQL 5.7 (With Bernard Spil's help), an introduction to &a.koobs; led to guidance on appropriate projects, such as Bugzilla development, helping Bugmeister, the Bugzilla Triage team, Developers, and the - Community by making issue tracking better. This is how things are + community by making issue tracking better. This is how things are going so far:

    Issue Tracking can be either "Defect Tracking for @@ -1727,8 +1727,8 @@

    • We have made improvements to the AutoAssigner module - (not yet deployed) that was previousely developed by Marcus to - assign ports' bugs to their maintainers by default, such as: + (not yet deployed) that was previously developed by Marcus to + assign port bugs to their maintainers by default, such as:
      • Improvements and bugfixes to port detection in @@ -1743,7 +1743,7 @@
      • We have developed a new module (FBSDAttachment), which automates setting maintainer-approval flag values on attachments under most conditions. This will improve time to resolution, - consistency of triage, and save manual effort on behalf of + consistency of triage, and reduce manual effort by triagers and maintainers.
      • We reported and upstreamed a number of bugs in Bugzilla, working @@ -1777,6 +1777,11 @@ + + Commit to Head + reboot(8) Manual Page Changes + +

        One of the long-missing features of &os; was the ability to boot up with a temporary rootfs, configure the kernel to be able @@ -1790,7 +1795,7 @@ init, and running the startup scripts as usual.

        The project is finished. All the relevant code has been committed - to &os; 11-CURRENT, and is expected to ship with &os; 11.0.

        + to &os; 11-CURRENT and is expected to ship with &os; 11.0.

        @@ -1817,10 +1822,10 @@ aims to fill that hole by making it possible to add RCTL rules for read bytes per second (BPS), write BPS, read I/O operations per second (IOPS), and write IOPS. It also adds a new throttling - mechanism, to delay process execution when a limit gets hit.

        + mechanism to delay process execution when a limit is reached.

        The project is at the late implementation stage. The major - piece of work left, apart from testing, is to integrate it with + piece of work left apart from testing is to integrate it with ZFS. The project is expected to ship with &os; 11.0.

        @@ -1847,7 +1852,7 @@

        The &os; Release Engineering Team is responsible for setting and publishing release schedules for official project releases - of &os;, announcing code freezes and maintaining the + of &os;, announcing code freezes, and maintaining the respective branches, among other things.

        During the last quarter of 2015, the Release Engineering team @@ -1863,7 +1868,7 @@

        Toward the end of the year, much of the primary focus was centered around the upcoming &os; 10.3 release cycle, - which will begin during January 2016.

        + which will begin in January 2016.

        As always, help testing development snapshot builds is crucial to producing quality releases, and we encourage @@ -1895,17 +1900,17 @@ -

        The goal of this project is to reimplement the exisitng +

        The goal of this project is to reimplement the existing MMC/SD stack using the CAM framework. This will permit utilizing the well-tested CAM locking model and debug features. - Additionally, it will be possible to process interrupts generated + It will also be possible to process interrupts generated by the inserted card, which is a prerequisite for implementing the SDIO interface.

        The first version of the code was uploaded to Phabricator for review. The new stack is able to attach to the SD - card and bring it to an operational state, so it is possible to - read and write to/from the card.

        + card and bring it to an operational state so it is possible to + read and write to the card.

        The only supported SD controller driver is ti_sdhci, which is used on the BeagleBone Black. @@ -1915,14 +1920,14 @@ -

        Rework bus/target/LUN enumeration and the locking model - — I don't really understand the CAM locking and am likely to +

        Rework bus/target/LUN enumeration and the locking model. + I do not really understand the CAM locking and am likely to do it incorrectly.

        -

        Modify the SDHCI driver on at least one x86 platform - — this will make development and collaboration easier.

        +

        Modify the SDHCI driver on at least one x86 platform. + This will make development and collaboration easier.

        @@ -1932,7 +1937,7 @@ - The Graphics stack on &os; + The Graphics Stack on &os; @@ -2005,7 +2010,7 @@ passwords kept in memory by a browser when a kernel panic occurred. An entity that can read data from a dump device or a crash directory can also extract this information from a core - dump. In order to prevent this situation, the core dump should be + dump. To prevent this situation, the core dump should be encrypted before it is stored on the dump device.

        This project allows a kernel to encrypt a core dump during @@ -2072,14 +2077,14 @@ involved with the &os; Project. This experimental pilot project has the task of setting up procedures for enhanced Issue (Problem Report) management that include better - classification/prioritization, eventually leading to faster - resolution of the issues.

        + classification and prioritization, eventually leading to faster + resolution of issues.

        We are now happy to report on the progress of this experimental team:

          -
        • We have set up the #FreeBSD-bugs IRC channel on +
        • The #FreeBSD-bugs IRC channel has been set up on Freenode and we are successfully using it to exchange information about triage processes, ask for help, propose changes and discuss related topics.
        • @@ -2098,9 +2103,9 @@
        • This experiment is benefiting from the introduction of newcomers to issue tracking. It naturally resulted in a entire - review of the tracking proccess from its very elementary aspects. + review of the tracking process from its very elementary aspects. This "fresh eyes" participation spotted minor details - along the proccess, giving the opportunity to scrutinize actual + along the process, giving the opportunity to scrutinize actual procedures on a number of smaller points, followed by proposals on how to improve the overall Issue Tracking and Management. The new ideas include both organizational and technical ideas and @@ -2108,10 +2113,11 @@ classification, the triage workflow, and Bugzilla technical improvements among others.
        • -
        • An important goal is producing documentation not only - aimed at people directly engaged on issue triage tasks, but also - documentation aimed at general users, about best practices for - using Bugzilla and the issue management workflow. Another +
        • An important goal is producing documentation about best + practices for using Bugzilla and issue management workflow. + This documentation should be aimed not only at people directly + engaged in issue triage tasks, but also at general users. + Another relevant point is that feedback from triage team can be used to improve Bugzilla in terms of adjusting existing features to best fit &os;'s needs, and development of new features (please see @@ -2126,7 +2132,7 @@ report.

        Since the Issue Triage Team is very young, we expect more - information be available and more actions be reported upon in the + information be available and more actions be reported in the next Status report.

        @@ -2152,7 +2158,7 @@
        - relaunchd + <tt>relaunchd</tt> @@ -2201,7 +2207,7 @@

        Add support for monitoring files and directories for - changes, and launching jobs when changes are detected.

        + changes and launching jobs when changes are detected.

        @@ -2210,14 +2216,14 @@ -

        Improve the documentation and providing more examples of - how to use it.

        +

        Improve the documentation and provide more examples of + usage.

        - &os; Integration Services (BIS) + &os; Integration Services (BIS) @@ -2243,21 +2249,22 @@ -

        When &os; virtual machines (VMs) run on Hyper-V, in order +

        When &os; virtual machines (VMs) run on Hyper-V, using + Hyper-V synthetic devices is recommended to get the best network and storage performance and make full use - of all the benefits that Hyper-V provides, it is recommended to - use Hyper-V synthetic devices. The collection of drivers that are + of all the benefits that Hyper-V provides. + The collection of drivers that are required to run Hyper-V synthetic devices in &os; are known as &os; Integration Services (BIS). Some of the BIS drivers (like network and storage drivers) have existed in &os; 9.x and 10.x for years, but there are still some performance and stability issues - and bugs. Additionally, compared with Windows and Linux VMs, the - current BIS lacks some important features, such as the virtual + and bugs. Compared with Windows and Linux VMs, the + current BIS lacks some important features, such as virtual Receive Side Scaling (vRSS) support in the Hyper-V network driver - and the support for UEFI VM (boot from UEFI), among others.

        + and support for UEFI VM (boot from UEFI), among others.

        We are now working more on the issues and performance - tuning to make &os; VM run better on Hyper-V and the Hyper-V based + tuning to make &os; VMs run better on Hyper-V and the Hyper-V based cloud platform Azure.

        Our work during 2015Q4 is documented below:

        @@ -2301,7 +2308,7 @@
      • Added ioctl support for SIOCGIFMEDIA for the Hyper-V network driver, fixing PR 187006 ([Hyper-V] dynamic - address (DHCP) obtaining doesn't work on HYPER-V OS + address (DHCP) obtaining does not work on HYPER-V OS 2012 R2).
      • Sent out patches to add an interrupt counter for @@ -2322,18 +2329,18 @@
    • -
    • We plan to add support for UEFI VMs (a.k.a., Hyper-V +
    • We plan to add support for UEFI VMs (Hyper-V Generation-2 VMs). Currently some issues and to-do items were - identified: e.g., we cannot use the i8254 PIT to calibrate the + identified. For example, we cannot use the i8254 PIT to calibrate the TSC because the i8254 PIT does not exist in a UEFI VM, and we need to add support for the Hyper-V synthetic keyboard/mouse/framebuffer device.
    • We are working on a disk detection issue: when a &os; VM runs on a Windows Server 2016 Technical Preview host, the VM - will detect 16 disks whereas only 1 disk is configured for the - VM. Due to this issue, VMs running on these hosts can fail to - boot. A workaround patch was made and we are trying to make a + will detect 16 disks when only one disk is configured for the + VM. VMs running on these hosts can fail to + boot. A workaround patch was created and we are trying to make a formal fix.
    • We are tidying up some internal BIS test cases and plan @@ -2347,7 +2354,7 @@ - Mellanox iSCSI Extensions For RDMA (iSER) Support + Mellanox iSCSI Extensions for RDMA (iSER) Support @@ -2404,7 +2411,7 @@ - Improvements for ARMv6/v7 support + Improvements for ARMv6/v7 Support @@ -2677,15 +2684,15 @@ scalability and the ability to add advanced features to the routing stack.

      -

      Currently, the packet output path suffers from excessive - locking, acquiring and releasing 4 distinct contested locks is - required in order to convert a packet to a frame suitable to put +

      The current packet output path suffers from excessive + locking. Acquiring and releasing four distinct contested locks is + required to convert a packet to a frame suitable to put on the wire. The first project goal is to reduce the number of locks needed to just two rmlock(9)s for the output path, which permits close-to-linear scaling.

      Since September, one of the locks (used to protect - link-level entries) is completely eliminated from the packet data + link-level entries) has been completely eliminated from the packet data path. A new routing API was introduced, featuring better scalability and hiding routing internals. Most of the consumers of the old routing API were converted to use the new API.

      @@ -2714,13 +2721,13 @@

      &a.bdrewery; (bdrewery@) has been working to improve the - build framework as well as buildworld build times. The build - system has largely been untouched by large-scale changes for many + build framework as well as buildworld build times. The build + system has been largely untouched by large-scale changes for many years. Most of the effort has been on improving the recent META_MODE merge that was presented at BSDCan 2014. This is a new build system that is not currently enabled by default but brings many benefits. Beyond that, some highlights of the work - changing buildworld are:

      + changing buildworld are:

      -

      Binary packages are available (only for test purposes) - which are regularly tested with the KDE development - repository.

      +

      Binary packages are available (only for test purposes) which + are regularly tested with the KDE development repository.

      @@ -838,14 +851,15 @@

      Node.js is a platform built on Chrome's JavaScript runtime - for easily building fast, scalable network applications. It uses - an event-driven, non-blocking I/O model that makes it lightweight - and efficient — perfect for data-intensive real-time applications - that run across distributed devices.

      + for easily building fast, scalable network applications. It + uses an event-driven, non-blocking I/O model that makes it + lightweight and efficient — perfect for data-intensive + real-time applications that run across distributed + devices.

      The goal of this project is to make it easy to install the - modules available in the npm package - registry.

      + modules available in the + npm package registry.

      Currently, the repository contains slightly fewer than 300 new ports, in particular:

      @@ -878,7 +892,8 @@ -

      Bring in grunt.js (and modules), the JavaScript task runner.

      +

      Bring in grunt.js (and modules), the JavaScript task + runner.

      @@ -949,17 +964,18 @@

      I recently became involved with &os; (as in, the last 2-3 - weeks), and found myself quickly involved with Ports development. - What struck me immediately was the difficulty in providing a Python - package that was depended upon by multiple versions of Python. As - it turns out, poudriere can currently only generate one package - per port, meaning that a Python version-neutral (compatible with - 2.x and 3.x) port cannot simultaneously be packaged for each - variant at the same time.

      + weeks), and found myself quickly involved with Ports + development. What struck me immediately was the difficulty in + providing a Python package that was depended upon by multiple + versions of Python. As it turns out, poudriere can currently + only generate one package per port, meaning that a Python + version-neutral (compatible with 2.x and 3.x) port cannot + simultaneously be packaged for each variant at the same + time.

      I discussed the issue with &a.koobs;, who suggested that I - look into implementing a "variants protocol" within the - Ports framework and the necessary changes to poudriere to + look into implementing a "variants protocol" within + the Ports framework and the necessary changes to poudriere to allow a port to generate more than one package.

      Support for variants is strongly needed in Ports and @@ -967,16 +983,16 @@

      • It would allow Python and other languages to provide - packages for dependencies for multiple language versions from the - same port.
      • + packages for dependencies for multiple language versions + from the same port.
      • It alleviates the need for so-called "slave - ports", as a single port could now have multiple generated - packages from a single port.
      • + ports", as a single port could now have multiple + generated packages from a single port.
      • It would have a very small impact on the greater Ports - ecosystem: adding only two new variables, VARIANT and - VARIANTS.
      • + ecosystem: adding only two new variables, VARIANT + and VARIANTS.
      • It would provide a more consistent approach between different packaging teams for handling variations.
      • @@ -991,24 +1007,25 @@ consistently generated by poudriere without issue.

        Fortunately, this is not a wishful thinking piece. I dug - in my heels and have implemented a proof-of-concept implementation - of variants in the Ports framework, including the necessary - modifications to poudriere in order to support it. It was mildly - upsettling to find that poudriere is mostly written in Bourne shell - scripts, but I pressed on nonetheless.

        - -

        I started with the - prototype made by &a.bapt; as a base, and built from there. - The poudriere PoC aims to limit changes as much as possible to - merely adding support for the new variants flags, while also at - the request of &a.koobs; making the logging output more - package-centric (as opposed to port-centric) as a result of these - changes.

        + in my heels and have implemented a proof-of-concept + implementation of variants in the Ports framework, including + the necessary modifications to poudriere in order to support + it. It was mildly upsettling to find that poudriere is mostly + written in Bourne shell scripts, but I pressed on + nonetheless.

        + +

        I started with + the prototype made by &a.bapt; + as a base, and built from there. The poudriere PoC aims to + limit changes as much as possible to merely adding support for + the new variants flags, while also at the request of &a.koobs; + making the logging output more package-centric (as opposed to + port-centric) as a result of these changes.

        This is a work in progress, and I would love to hear your feedback. I have enjoyed my first few weeks - working on &os;, and I hope to stay here for quite some time.

        + working on &os;, and I hope to stay here for quite some + time.

        @@ -1018,8 +1035,8 @@ -

        Hopefully the code will be of sufficient quality to be considered - for formal review in the coming months.

        +

        Hopefully the code will be of sufficient quality to be + considered for formal review in the coming months.

        @@ -1045,46 +1062,46 @@ -

        When I starting working on ports for &os; in the last - couple of weeks, I found that my workflow was not as efficient as - it could be using just the available tools, so I made a few that +

        When I starting working on ports for &os; in the last couple + of weeks, I found that my workflow was not as efficient as it + could be using just the available tools, so I made a few that could be useful to the development community at large. All of - these have been or will soon be added to the Ports tree, - so you can play with them today!

        + these have been or will soon be added to the Ports tree, so + you can play with them today!

        pytoport is a command-line application that generates a skeleton port for a given PyPI package name. It attempts to generate the correct dependencies, makes a good - attempt at guessing the license using spdx-lookup, and - generates a pkg-descr. This made generating the fifteen - or so ports I was working on a complete breeze.

        + attempt at guessing the license using spdx-lookup, + and generates a pkg-descr. This made generating the + fifteen or so ports I was working on a complete breeze.

        While doing this, however, I noticed that some ports were - bringing in dependencies that I did not expect, and I needed some - way to visualise this. skog builds a dependency tree - from the depends lists output by the Ports framework, and displays - it on the command line (with extra shiny output if you are using - UTF-8). No more pesky example and documentation dependencies - being dragged in when you clearly toggled that - OPTION as far off as it would go.

        - -

        While doing all of this, I found it cumbersome to be - copying ports back and forth between my small development tree - living in git and the larger upstream SVN tree I was using in + bringing in dependencies that I did not expect, and I needed + some way to visualise this. skog builds a dependency + tree from the depends lists output by the Ports framework, and + displays it on the command line (with extra shiny output if + you are using UTF-8). No more pesky example and documentation + dependencies being dragged in when you clearly + toggled that OPTION as far off as it would go.

        + +

        While doing all of this, I found it cumbersome to be copying + ports back and forth between my small development tree living + in git and the larger upstream SVN tree I was using in poudriere. I built a tool called bandar that takes - advantage of the FUSE version of unionfs to easily overlay my dev - tree on the upstream tree, run linting, poudriere, and generate - archives with ease.

        + advantage of the FUSE version of unionfs to easily overlay my + dev tree on the upstream tree, run linting, poudriere, and + generate archives with ease.

        I am very impressed with how easy it was to build more - tooling for &os;. I hope some of these tools will be of some use - to you, and as always, I'd love to hear your feedback!

        + tooling for &os;. I hope some of these tools will be of some + use to you, and as always, I'd love to hear your feedback!

        -

        Improve skog to support searching a tree for a certain - port.

        +

        Improve skog to support searching a tree for a + certain port.

        @@ -1092,8 +1109,8 @@ -

        Continue to improve pytoport, adding trove support and better - dependency handling.

        +

        Continue to improve pytoport, adding + trove support and better dependency handling.

        @@ -1118,68 +1135,70 @@

        The Out of Memory (OOM) code is intended to handle the situation where the system needs free memory to make progress, - but no memory can be reused. Most often, the situation is that - to free memory, the system needs more free memory. Consider a - case where the system needs to page-out dirty pages, but needs to - allocate structures to track the writes. OOM "solves" - the problem by killing some selection of user processes. In other - words, it trades away system deadlock by suffering a partial loss - of user data. The assumption is that it is better to kill a - process and recover data in other processes than to lose - everything.

        + but no memory can be reused. Most often, the situation is + that to free memory, the system needs more free memory. + Consider a case where the system needs to page-out dirty + pages, but needs to allocate structures to track the writes. + OOM "solves" the problem by killing some selection + of user processes. In other words, it trades away system + deadlock by suffering a partial loss of user data. The + assumption is that it is better to kill a process and recover + data in other processes than to lose everything.

        Free memory in the &os; Virtual Memory (VM) system appears - from two sources. One is the voluntary reclamation of pages used - by a process, for example unmapping private anonymous regions, or - the last unlink of an otherwise unreferenced file with cached - pages. Another source is the pagedaemon, which forcefully frees - pages which carry data, of course after the data is moved to some - other storage, like swap or file blocks. OOM is triggered when - the pagedaemon definitely cannot free memory to satisfy the - requests.

        - -

        The old criteria to trigger the OOM action was a combination of - low free swap space and a low count of free pages (the latter is - expressed precisely with the paging targets constants, but this is - not relevant to the discussion). That test is mostly incorrect. - For example, a low free page state might be caused by a greedy consumer - allocating all pages freed by the page daemon in the current pass, - but this does not preclude the page daemon from producing more - pages. Also, since page-outs are asynchronous, the previous page - daemon pass might not immmediately produce any free pages, but - they would appear some short time later.

        + from two sources. One is the voluntary reclamation of pages + used by a process, for example unmapping private anonymous + regions, or the last unlink of an otherwise unreferenced file + with cached pages. Another source is the pagedaemon, which + forcefully frees pages which carry data, of course after the + data is moved to some other storage, like swap or file blocks. + OOM is triggered when the pagedaemon definitely cannot free + memory to satisfy the requests.

        + +

        The old criteria to trigger the OOM action was a combination + of low free swap space and a low count of free pages (the + latter is expressed precisely with the paging targets + constants, but this is not relevant to the discussion). That + test is mostly incorrect. For example, a low free page state + might be caused by a greedy consumer allocating all pages + freed by the page daemon in the current pass, but this does + not preclude the page daemon from producing more pages. Also, + since page-outs are asynchronous, the previous page daemon + pass might not immmediately produce any free pages, but they + would appear some short time later.

        More seriously, low swap space does not necessarily indicate that we are in trouble: lots of pages might not require swap - allocations to be freed, like clean pages or pages backed by files. - The last notion is serious, since swap-less systems were - considered as having full swap.

        - -

        Instead of trying to deduce the deadlock from looking at - the current VM state, the new OOM handler tracks the history of - page daemon passes. Only when several consequtive passes failed to - meet the paging target is an OOM kill considered necessary. The - count of consequent failed passes was selected empirically, by - testing on small (32M) and large (512G) machines. Auto-tuning of - the counter is possible, but requires some more architectural - changes to the I/O subsystem.

        + allocations to be freed, like clean pages or pages backed by + files. The last notion is serious, since swap-less systems + were considered as having full swap.

        + +

        Instead of trying to deduce the deadlock from looking at the + current VM state, the new OOM handler tracks the history of + page daemon passes. Only when several consequtive passes + failed to meet the paging target is an OOM kill considered + necessary. The count of consequent failed passes was selected + empirically, by testing on small (32M) and large (512G) + machines. Auto-tuning of the counter is possible, but + requires some more architectural changes to the I/O + subsystem.

        -

        Another issue was identified with the algorithm which - selects a victim process for OOM kill. It compared the counts of +

        Another issue was identified with the algorithm which selects + a victim process for OOM kill. It compared the counts of pages mapping entries (PTEs) installed into the machine paging structures. For different reasons, machine-dependent VM code - (pmap) may remove the pte for a memory-resident page. Under some - circumstances related to other measures to prevent low memory - deadlock, very large processes which consume all system memory - could have few or no ptes. The old OOM selector ignored the - process which caused the deadlock, killing unrelated - processes.

        - -

        A new function, vm_pageout_oom_pagecount(), was written which - applies a reasonable heuristic to estimate the number of pages - freed by killing the given process. This - eliminates the effect of selecting small unrelated processes for - OOM kill.

        + (pmap) may remove the pte for a memory-resident page. Under + some circumstances related to other measures to prevent low + memory deadlock, very large processes which consume all system + memory could have few or no ptes. The old OOM selector + ignored the process which caused the deadlock, killing + unrelated processes.

        + +

        A new function, vm_pageout_oom_pagecount(), was + written which applies a reasonable heuristic to estimate the + number of pages freed by killing the given process. This + eliminates the effect of selecting small unrelated processes + for OOM kill.

        The rewrite was committed to HEAD in r290917 and r290920.

        @@ -1205,15 +1224,16 @@ -

        A new driver, cxgbei, enabling hardware - accelerated iSCSI with Chelsio's T5- and T4-based offload-capable - cards, has been committed to HEAD. Both Initiator and Target are - supported. The wire traffic is standard iSCSI (SCSI over TCP as - per RFC 3720, etc.) so an Initiator/Target using this driver will - interoperate with all other standards-compliant +

        A new driver, cxgbei, enabling hardware accelerated + iSCSI with Chelsio's T5- and T4-based offload-capable cards, + has been committed to HEAD. Both Initiator and Target are + supported. The wire traffic is standard iSCSI (SCSI over TCP + as per RFC 3720, etc.) so an Initiator/Target using this + driver will interoperate with all other standards-compliant implementations.

        -

        Hardware assistance provided by the T5 and T4 ASICs includes:

        +

        Hardware assistance provided by the T5 and T4 ASICs + includes:

        • Complete TCP processing.
        • @@ -1240,8 +1260,9 @@

          The driver is in advanced stage QA and will see some - bugfixes and performance enhancements in the very near future. - MFC is possible as soon as the QA cycle completes.

          + bugfixes and performance enhancements in the very near + future. MFC is possible as soon as the QA cycle + completes.

          @@ -1280,16 +1301,16 @@

          OpenBSM is a BSD-licensed implementation of Sun's Basic - Security Module (BSM) API and file format. It is the user-space - side of the CAPP Audit implementations in &os; and Mac OS X. - Additionally, the audit trail processing tools are expected to - work on Linux.

          + Security Module (BSM) API and file format. It is the + user-space side of the CAPP Audit implementations in &os; and + Mac OS X. Additionally, the audit trail processing tools are + expected to work on Linux.

          Progress has been slow but steady this quarter, culminating in OpenBSM 1.2 alpha 4, the first release in three years. It features various bug fixes and documentation improvements; the - complete list of changes is documented in the NEWS + complete list of changes is documented in the + NEWS file on GitHub. The release was imported into &os; HEAD and merged to &os; 10-STABLE. As such it will be part of &os; 10.3-RELEASE.

          @@ -1297,9 +1318,9 @@ -

          Test the new release on different versions of &os;, Mac - OS X, and Linux. In particular, testing on Mac OS X 10.9 (Mavericks) - and newer would be greatly appreciated.

          +

          Test the new release on different versions of &os;, Mac OS + X, and Linux. In particular, testing on Mac OS X 10.9 + (Mavericks) and newer would be greatly appreciated.

          @@ -1354,12 +1375,12 @@ *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-head@freebsd.org Sun Jan 31 22:50:23 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6F949A74B08; Sun, 31 Jan 2016 22:50:23 +0000 (UTC) (envelope-from wblock@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3CDBE1E3E; Sun, 31 Jan 2016 22:50:23 +0000 (UTC) (envelope-from wblock@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u0VMoMHU028339; Sun, 31 Jan 2016 22:50:22 GMT (envelope-from wblock@FreeBSD.org) Received: (from wblock@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u0VMoMHW028338; Sun, 31 Jan 2016 22:50:22 GMT (envelope-from wblock@FreeBSD.org) Message-Id: <201601312250.u0VMoMHW028338@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: wblock set sender to wblock@FreeBSD.org using -f From: Warren Block Date: Sun, 31 Jan 2016 22:50:22 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r48134 - head/en_US.ISO8859-1/htdocs/news/status X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Jan 2016 22:50:23 -0000 Author: wblock Date: Sun Jan 31 22:50:21 2016 New Revision: 48134 URL: https://svnweb.freebsd.org/changeset/doc/48134 Log: Fix a reversed comma and period. Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Sun Jan 31 22:49:41 2016 (r48133) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Sun Jan 31 22:50:21 2016 (r48134) @@ -3718,7 +3718,7 @@ -

          We plan to commit the rest of userspace (i.e,. libc), +

          We plan to commit the rest of userspace (i.e., libc), kernel support, etc., in a few weeks.

          From owner-svn-doc-head@freebsd.org Mon Feb 1 03:25:29 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 09C3EA7499B; Mon, 1 Feb 2016 03:25:29 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C921E1ED9; Mon, 1 Feb 2016 03:25:28 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u113PRnu011160; Mon, 1 Feb 2016 03:25:27 GMT (envelope-from gjb@FreeBSD.org) Received: (from gjb@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u113PRpd011157; Mon, 1 Feb 2016 03:25:27 GMT (envelope-from gjb@FreeBSD.org) Message-Id: <201602010325.u113PRpd011157@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: gjb set sender to gjb@FreeBSD.org using -f From: Glen Barber Date: Mon, 1 Feb 2016 03:25:27 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r48135 - in head/en_US.ISO8859-1/htdocs/releases: 10.2R 9.3R X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Feb 2016 03:25:29 -0000 Author: gjb Date: Mon Feb 1 03:25:27 2016 New Revision: 48135 URL: https://svnweb.freebsd.org/changeset/doc/48135 Log: Regen after r295115 Sponsored by: The FreeBSD Foundation Modified: head/en_US.ISO8859-1/htdocs/releases/10.2R/errata.html head/en_US.ISO8859-1/htdocs/releases/9.3R/errata.html Modified: head/en_US.ISO8859-1/htdocs/releases/10.2R/errata.html ============================================================================== --- head/en_US.ISO8859-1/htdocs/releases/10.2R/errata.html Sun Jan 31 22:50:21 2016 (r48134) +++ head/en_US.ISO8859-1/htdocs/releases/10.2R/errata.html Mon Feb 1 03:25:27 2016 (r48135) @@ -1,5 +1,5 @@ -FreeBSD 10.2-RELEASE Errata

          FreeBSD 10.2-RELEASE Errata

          The FreeBSD Project

          FreeBSD 10.2-RELEASE Errata

          The FreeBSD Project

          FreeBSD is a registered trademark of the FreeBSD Foundation.

          Intel, Celeron, Centrino, Core, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or registered @@ -41,6 +41,7 @@ vulnerability

          FreeBSD-SA-16:05.tcp14 January 2016

          MD5 signature denial of service

          FreeBSD-SA-16:06.bsnmpd14 January 2016

          Insecure default configuration file permissions

          FreeBSD-SA-16:07.openssh14 January 2016

          OpenSSH client information leak

          FreeBSD-SA-16:09.ntp27 January 2016

          Multiple vulnerabilities.

          FreeBSD-SA-16:10.linux27 January 2016

          issetugid(2) system call + vulnerability.

          FreeBSD-SA-16:11.openssl30 January 2016

          SSLv2 cipher suite downgrade vulnerability.

          3. Errata Notices

          ErrataDateTopic
          FreeBSD-EN-15:11.toolchain18 August 2015

          Fix make(1) syntax errors when upgrading from FreeBSD 9.x and earlier.

          FreeBSD-EN-15:12.netstat18 August 2015

          Fix incorrect netstat(1) data handling on 32-bit systems.

          FreeBSD-EN-15:13.vidcontrol18 August 2015

          Allow size argument to vidcontrol(1) for Modified: head/en_US.ISO8859-1/htdocs/releases/9.3R/errata.html ============================================================================== --- head/en_US.ISO8859-1/htdocs/releases/9.3R/errata.html Sun Jan 31 22:50:21 2016 (r48134) +++ head/en_US.ISO8859-1/htdocs/releases/9.3R/errata.html Mon Feb 1 03:25:27 2016 (r48135) @@ -1,5 +1,5 @@ -FreeBSD 9.3-RELEASE Errata

          FreeBSD 9.3-RELEASE Errata

          +FreeBSD 9.3-RELEASE Errata

          FreeBSD 9.3-RELEASE Errata

          The FreeBSD Project

          FreeBSD is a registered trademark of the FreeBSD Foundation.

          Intel, Celeron, Centrino, Core, EtherExpress, i386, @@ -62,6 +62,7 @@ permissions

          FreeBSD-SA-16:07.openssh14 January 2016

          OpenSSH client information leak

          FreeBSD-SA-16:08.bind27 January 2016

          Remote denial of service vulnerability.

          FreeBSD-SA-16:09.ntp27 January 2016

          Multiple vulnerabilities.

          FreeBSD-SA-16:10.linux27 January 2016

          issetugid(2) system call + vulnerability.

          FreeBSD-SA-16:11.openssl30 January 2016

          SSLv2 cipher suite downgrade vulnerability.

          3. Errata Notices

          ErrataDateTopic
          FreeBSD-EN-14:10.tzdata21 October 2014

          Time zone data file update

          FreeBSD-EN-14:11.crypt21 October 2014

          Change crypt(3) default hashing algorithm back to DES

          FreeBSD-EN-14:12.zfs11 November 2014

          Fix NFSv4 and ZFS cache consistency issue

          FreeBSD-EN-14:13.freebsd-update23 December 2014

          Fixed directory deletion issue in From owner-svn-doc-head@freebsd.org Mon Feb 1 04:48:38 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3ABF3A75EF6; Mon, 1 Feb 2016 04:48:38 +0000 (UTC) (envelope-from bjk@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EB41FA9B; Mon, 1 Feb 2016 04:48:37 +0000 (UTC) (envelope-from bjk@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u114maYX034250; Mon, 1 Feb 2016 04:48:36 GMT (envelope-from bjk@FreeBSD.org) Received: (from bjk@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u114maBT034249; Mon, 1 Feb 2016 04:48:36 GMT (envelope-from bjk@FreeBSD.org) Message-Id: <201602010448.u114maBT034249@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bjk set sender to bjk@FreeBSD.org using -f From: Benjamin Kaduk Date: Mon, 1 Feb 2016 04:48:36 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r48136 - head/en_US.ISO8859-1/htdocs/news/status X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Feb 2016 04:48:38 -0000 Author: bjk Date: Mon Feb 1 04:48:36 2016 New Revision: 48136 URL: https://svnweb.freebsd.org/changeset/doc/48136 Log: Add an introduction to the 2015Q4 report Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Mon Feb 1 03:25:27 2016 (r48135) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Mon Feb 1 04:48:36 2016 (r48136) @@ -20,19 +20,46 @@ an announcement email is sent to the &os;-Announce mailing list.

          - This report covers &os;-related projects between October and - December 2015. This is the last of four reports planned for - 2015.

          +

          The fourth quarter of 2015 saw a great deal of activity for + &os;. This is now the third quarter running for which I can say + that this is the largest report yet published! Many thanks to the + developers who proactively submitted topics and entries — it + is great to have more complete coverage of ongoing development for + the community to learn about in these reports.

          + +

          An experimental new team was formed this quarter to triage + newly-reported bugs and improve the procedures and tooling for + managing bug submissions. Making more effective use of automation + and tooling can help to increase developer productivity and the + quality of &os;, just as the adoption of Jenkins and continual + integration tooling catches regressions quickly and maintains the + high standards for the system.

          + +

          Efforts to bring our BSD high standards to new + architectures continue, with impressive work on arm64 leading to + its promotion to Tier-2 status and a flurry of work bringing up + the new RISC-V hardware architecture. Software architecture is + also under active development, including system startup and + service management. A handful of potential init system + replacements are mentioned in this report: launchd, + relaunchd, and nosh. Architectural changes + originating both from academic research (multipath TCP) and from + the realities of industry (sendfile(2) improvements) are + also under way. It is heartening to see how &os; provides a + welcoming platform for contributions from both research and + industry.

          + +

          To all the readers, whether from academia or industry, + hobbyist or professional: I hope you are as excited as I am to + read about all of the progress and projects covered in this + report, and the future of &os;!

          -

          The fourth quarter of 2015 was another productive quarter for - the &os; project and community. [...]

          +

          —Ben Kaduk

          -

          Thanks to all the reporters for the excellent work!

          +


          The deadline for submissions covering the period from January to March 2016 is April 7, 2016.

          - ?> From owner-svn-doc-head@freebsd.org Mon Feb 1 06:01:15 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8B35BA903B2; Mon, 1 Feb 2016 06:01:15 +0000 (UTC) (envelope-from bjk@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 12420122C; Mon, 1 Feb 2016 06:01:15 +0000 (UTC) (envelope-from bjk@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u1161ESx057425; Mon, 1 Feb 2016 06:01:14 GMT (envelope-from bjk@FreeBSD.org) Received: (from bjk@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u1161EeX057424; Mon, 1 Feb 2016 06:01:14 GMT (envelope-from bjk@FreeBSD.org) Message-Id: <201602010601.u1161EeX057424@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bjk set sender to bjk@FreeBSD.org using -f From: Benjamin Kaduk Date: Mon, 1 Feb 2016 06:01:14 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r48137 - head/en_US.ISO8859-1/htdocs/news/status X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Feb 2016 06:01:15 -0000 Author: bjk Date: Mon Feb 1 06:01:13 2016 New Revision: 48137 URL: https://svnweb.freebsd.org/changeset/doc/48137 Log: First half of an editing pass on the 2015Q4 report wblock has already done the heavy lifting, so this diff is not quite so big. Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Mon Feb 1 04:48:36 2016 (r48136) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Mon Feb 1 06:01:13 2016 (r48137) @@ -674,13 +674,13 @@ For example, 9% of 75% of MAXVNODES is more than 566000 vnodes to reclaim whenever vnlru_proc() becomes active.

          -

          The vfs.vlru_alloc_cache_src sysctl is removed. New +

          The vfs.vlru_alloc_cache_src sysctl is removed. The new code frees namecache sources as the last chance to satisfy the highest watermark, instead of selecting source vnodes randomly. This provides good enough behavior to keep vn_fullpath() working in most situations. Filesystem layouts with deep trees, where the removed knob was required, - is thus handled automatically.

          + are thus handled automatically.

          As the kernel allocates and frees vnodes, it fully initializes them on every allocation and fully releases them @@ -733,7 +733,7 @@ from ancient 1Gbps 22xx to modern 16Gbps 26xx.

        • Port database handling was unified for target and - initiator roles, allowing HBA port to play both roles at the + initiator roles, allowing an HBA port to play both roles at the same time.
        • The maximal number of ports was increased from 256 to @@ -1202,7 +1202,7 @@

          Instead of trying to deduce the deadlock from looking at the current VM state, the new OOM handler tracks the history of - page daemon passes. Only when several consequtive passes + page daemon passes. Only when several consecutive passes failed to meet the paging target is an OOM kill considered necessary. The count of consequent failed passes was selected empirically, by testing on small (32M) and large (512G) @@ -1213,7 +1213,7 @@

          Another issue was identified with the algorithm which selects a victim process for OOM kill. It compared the counts of pages mapping entries (PTEs) installed into the machine paging - structures. For different reasons, machine-dependent VM code + structures. For different reasons, the machine-dependent VM code (pmap) may remove the pte for a memory-resident page. Under some circumstances related to other measures to prevent low memory deadlock, very large processes which consume all system @@ -1339,7 +1339,7 @@ complete list of changes is documented in the NEWS file on GitHub. The release was imported into &os; HEAD and - merged to &os; 10-STABLE. As such it will be part of &os; + merged to &os; 10-STABLE. As such, it will be part of &os; 10.3-RELEASE.

          @@ -1762,9 +1762,9 @@

          The bugmeister team has gained a new member, Mahdi Mokhtari (mokhi64@gmail.com). Mahdi has been contributing to the &os; Project for just over one month. After getting started by - creating ports for Chef-Server and MySQL 5.7 (With Bernard + creating ports for Chef-Server and MySQL 5.7 (with Bernard Spil's help), an introduction to &a.koobs; led to guidance on - appropriate projects, such as Bugzilla development, helping + appropriate projects, such as Bugzilla development to help Bugmeister, the Bugzilla Triage team, Developers, and the community by making issue tracking better. This is how things are going so far:

          @@ -1781,7 +1781,7 @@
          • We have made improvements to the AutoAssigner module - (not yet deployed) that was previously developed by Marcus + (not yet deployed) that was previously developed by &a.mva; to assign port bugs to their maintainers by default, such as: @@ -1924,8 +1924,8 @@ Of note, the release build code no longer produces MD5 checksums, in favor of SHA512.

            -

            Toward the end of the year, much of the primary focus was - centered around the upcoming &os; 10.3 release cycle, +

            Toward the end of the year, focus was primarily + centered on the upcoming &os; 10.3 release cycle, which will begin in January 2016.

            As always, help testing development snapshot builds is @@ -2081,7 +2081,7 @@ files.

            A patch has been uploaded to Phabricator for review. The - project is currently being updated to address the review + patch is currently being updated to address the review comments, and should be committed as soon as it is accepted. For more technical details, please visit the FreeBSD-security mailing list archive or see the Phabricator review.

            @@ -2167,22 +2167,22 @@ newcomers to issue tracking. It naturally resulted in a entire review of the tracking process from its very elementary aspects. This "fresh eyes" - participation spotted minor details along the process, + participation spotted minor details during the process, giving the opportunity to scrutinize actual procedures on a number of smaller points, followed by proposals on how to improve the overall Issue Tracking and Management. The new ideas include both organizational and technical ideas and solutions, such as new or modified keywords or flags for better classification, the triage workflow, and Bugzilla - technical improvements among others.
          • + technical improvements, among others.
          • An important goal is producing documentation about best practices for using Bugzilla and issue management workflow. This documentation should be aimed not only at people directly engaged in issue triage tasks, but also at general - users. Another relevant point is that feedback from triage + users. Another relevant point is that feedback from the triage team can be used to improve Bugzilla in terms of adjusting - existing features to best fit &os;'s needs, and development + existing features to best fit &os;'s needs, and the development of new features (please see Mahdi "Magic" Mokhtari's report on "Bugzilla improvements").
          • @@ -2195,13 +2195,13 @@ linked in this report.

          Since the Issue Triage Team is very young, we expect more - information be available and more actions be reported in the - next Status report.

          + information be available and more actions to be reported in the + next status report.

          -

          Set up the Wiki namespace and organize the brainstorm +

          Set up the Wiki namespace and organize the brainstorming document into a meaningful set of documents.

          @@ -2379,7 +2379,7 @@
        • Sent out patches to add an interrupt counter for Hyper-V VMBus interrupts (so the user can easily get - the statistical information about VMBus interrupts), + statistical information about VMBus interrupts), and fix the KVP daemon's poll timeout (so the daemon will avoid unnecessary polling every 100 milliseconds.
        • @@ -2454,7 +2454,7 @@ capabilities of Mellanox's 10, 40, 56, and 100 Gigabit Infiniband (IB)/Ethernet adapters.

          -

          Remote Direct Memory Access (RDMA) has been shown to have a +

          Remote Direct Memory Access (RDMA) has been shown to have great value for storage applications. RDMA infrastructure provides benefits such as zero-copy, CPU offload, reliable transport, fabric consolidation, and many more. The iSER @@ -2584,7 +2584,7 @@ Deputy Security Officer. Accordingly, the role of the SO team has been redefined to be the controller of the distribution of security sensitive information into and - within the project; they are responsible for interfacing + within the project: they are responsible for interfacing with external bodies and individuals reporting security problems to the project, and connecting those reports to the appropriate individuals within the project with the @@ -2616,8 +2616,9 @@ for other (Tier 2 or below) architectures is not yet of sufficient quality to be viable, and the older but pre-existing GPLv2 toolchain cannot support some of the - interesting new architectures such as arm64 and RISC V. - Pragmatically, in order for the project to support these, + interesting new architectures such as arm64 and RISC-V. + Pragmatically, in order for the project to support + these architectures, until LLVM support arrives we must turn to the GNU project's GPLv3 licenced toolchain.

          @@ -2668,9 +2669,9 @@ authorial attributions for sections of documentation, some of which may only be a few words long. Unlike source code, blocks of documentation are frequently moved around within - individual files, or even between files. Consequently Core - would like to introduce a "Voluntary Contribution - Agreement" along the lines of the one operated by the + individual files, or even between files. Consequently, Core + would like to introduce a Voluntary Contribution + Agreement along the lines of the one operated by the Apache Foundation. With this, copyrights are signed over to the &os; Foundation, with individual contributions being recognised by recording names in a general @@ -2721,7 +2722,7 @@

          No commit bits were taken in during the quarter. A non-committer account was approved for Kevin Bowling of LimeLight Networks. Kevin will be doing systems - administration work with clusteradm with particular interest + administration work with clusteradm, with particular interest in the parts of the cluster that are now hosted in LLNW's facilities. Deb Goodkin of the &os; Foundation was added to the developers mailing list: she was one of the few members of @@ -3504,7 +3505,8 @@ can generate a sequence of commands to check out the ports tree from Subversion, apply the patch, and then invoke poudriere to build the affected part of the ports - tree. Ricky consulted with Torsten Zühlsdorff on this. + tree. Ricky consulted with Torsten Zühlsdorff + during its development. This script will be used later to test changes to the ports tree. @@ -3577,7 +3579,7 @@

        • Michael Zhilin fixed the Akuma library for &os;. The Akuma library is used by Jenkins to determine what command-line arguments were passed to a running process. To - fix this, Michael invoked an &os;-specific sysctl() + fix it, Michael invoked an &os;-specific sysctl() with KERN_PROC_ARGS to determine the arguments for a running pid. This fix allows a running Jenkins instance to restart itself after new plugins are installed.
        • @@ -4207,7 +4209,7 @@ loader(8). Other devices may be loaded there, or early in the boot (depending on which gives better performance). Users will still be able to run more - "monolithic" configurations, as well as limit which + monolithic; configurations, as well as limit which kernel modules are available as can be done today, though without the convenience that automatic loading will provide. This work remains ongoing.

          @@ -4316,7 +4318,7 @@ 28th and a 29th (from PC-BSD 10.2) added. Items crossed off by version 1.24 include (amongst others) mfs support for /tmp, static ARP and networking, persistent - "entropy" for the randomness subsystem, + entropy for the randomness subsystem, pefs, and hald.

          The remaining items in the task list are mostly aimed at From owner-svn-doc-head@freebsd.org Mon Feb 1 16:26:56 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BAB57A972D3; Mon, 1 Feb 2016 16:26:56 +0000 (UTC) (envelope-from wblock@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8DD9815EC; Mon, 1 Feb 2016 16:26:56 +0000 (UTC) (envelope-from wblock@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u11GQtvO042448; Mon, 1 Feb 2016 16:26:55 GMT (envelope-from wblock@FreeBSD.org) Received: (from wblock@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u11GQtA6042447; Mon, 1 Feb 2016 16:26:55 GMT (envelope-from wblock@FreeBSD.org) Message-Id: <201602011626.u11GQtA6042447@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: wblock set sender to wblock@FreeBSD.org using -f From: Warren Block Date: Mon, 1 Feb 2016 16:26:55 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r48138 - head/en_US.ISO8859-1/htdocs/news/status X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Feb 2016 16:26:56 -0000 Author: wblock Date: Mon Feb 1 16:26:55 2016 New Revision: 48138 URL: https://svnweb.freebsd.org/changeset/doc/48138 Log: Change teachbsd.com to .org and add the important words "open source" to that entry. Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Mon Feb 1 06:01:13 2016 (r48137) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Mon Feb 1 16:26:55 2016 (r48138) @@ -3166,8 +3166,8 @@

          &a.gnn; and &a.rwatson; announced the release of their TeachBSD initiative: - http://teachbsd.com/. - TeachBSD offers a set of reusable course materials designed to + http://teachbsd.org/. + TeachBSD offers a set of open source reusable course materials designed to allow others to teach both university students and software practitioners &os; operating system fundamentals. The Foundation is proud to have partly sponsored their efforts to From owner-svn-doc-head@freebsd.org Tue Feb 2 04:40:09 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6EE85A9848F; Tue, 2 Feb 2016 04:40:09 +0000 (UTC) (envelope-from bjk@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 38EC5BB6; Tue, 2 Feb 2016 04:40:09 +0000 (UTC) (envelope-from bjk@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u124e8ZQ061590; Tue, 2 Feb 2016 04:40:08 GMT (envelope-from bjk@FreeBSD.org) Received: (from bjk@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u124e8SC061589; Tue, 2 Feb 2016 04:40:08 GMT (envelope-from bjk@FreeBSD.org) Message-Id: <201602020440.u124e8SC061589@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bjk set sender to bjk@FreeBSD.org using -f From: Benjamin Kaduk Date: Tue, 2 Feb 2016 04:40:08 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r48139 - head/en_US.ISO8859-1/htdocs/news/status X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Feb 2016 04:40:09 -0000 Author: bjk Date: Tue Feb 2 04:40:07 2016 New Revision: 48139 URL: https://svnweb.freebsd.org/changeset/doc/48139 Log: Finish up my editing pass Among other things, use just "head" to talk about the development branch, not "HEAD". Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Mon Feb 1 16:26:55 2016 (r48138) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Tue Feb 2 04:40:07 2016 (r48139) @@ -169,8 +169,9 @@ - Bruce's email requesting bool be added to style(9) - Differential Revision for the change + Bruce's Email Requesting bool be Added to style(9) + Differential Revision for the Change @@ -366,7 +367,7 @@ &os; on Odroid-C1 - Commit adding glue driver + Commit Adding Glue Driver @@ -465,7 +466,7 @@ - New 1:1-only thread target for &os; + New 1:1-Only Thread Target for &os; @@ -473,7 +474,7 @@ devel/gdb port.

          Changes to support cross-debugging of crashdumps in libkvm - were committed to HEAD in r291406.

          + were committed to head in r291406.

          A new thread target for &os; that is suitable for merging upstream has been written and lightly tested. However, it is @@ -571,7 +572,7 @@ Beaglebone Black with 4DCAPE-43T Demo Input Stack Plans - evdev Port + evdev Port @@ -582,13 +583,13 @@

          Proper touchscreen support would consist of a userland event reading API, a kernel event reporting API, and kernel hardware drivers for specific devices. There is an ongoing effort to - port the Linux evdev API to &os; so applications that use + port the Linux evdev API to &os; so applications that use libraries like libinput or tslib could be used without any major changes. Since it is not yet complete, I created a - naive evdev-like API for both kernel and tslib and was able to + naive evdev-like API for both kernel and tslib and was able to run a demo on a Beaglebone Black with 4DCAPE-43T.

          -

          Once evdev makes it into the tree, both hardware drivers +

          Once evdev makes it into the tree, both hardware drivers can be modified to include "report events" portions and committed.

          @@ -1083,9 +1084,9 @@ pytoport: Generate &os; Ports from Python modules on PyPI - bandar: Create Development Overlays for the Ports tree + bandar: Create Development Overlays for the Ports Tree skog: Generate Visual Dependency Trees for &os; Ports - spdx-lookup: SPDX License List Query Tool + spdx-lookup: SPDX License List Query Tool @@ -1117,7 +1118,7 @@ in git and the larger upstream SVN tree I was using in poudriere. I built a tool called bandar that takes advantage of the FUSE version of unionfs to easily overlay my - dev tree on the upstream tree, run linting, poudriere, and + dev tree on the upstream tree, run lint checks, poudriere, and generate archives with ease.

          I am very impressed with how easy it was to build more @@ -1227,7 +1228,7 @@ eliminates the effect of selecting small unrelated processes for OOM kill.

          -

          The rewrite was committed to HEAD in r290917 and r290920.

          +

          The rewrite was committed to head in r290917 and r290920.

          The FreeBSD Foundation @@ -1253,7 +1254,7 @@

          A new driver, cxgbei, enabling hardware accelerated iSCSI with Chelsio's T5- and T4-based offload-capable cards, - has been committed to HEAD. Both Initiator and Target are + has been committed to head. Both Initiator and Target are supported. The wire traffic is standard iSCSI (SCSI over TCP as per RFC 3720, etc.) so an Initiator/Target using this driver will interoperate with all other standards-compliant @@ -1338,7 +1339,7 @@ features various bug fixes and documentation improvements; the complete list of changes is documented in the NEWS - file on GitHub. The release was imported into &os; HEAD and + file on GitHub. The release was imported into &os; head and merged to &os; 10-STABLE. As such, it will be part of &os; 10.3-RELEASE.

          @@ -1434,7 +1435,7 @@

          The port is under community review and will be integrated - into HEAD soon.

          + into head soon.

          @@ -1467,7 +1468,7 @@ - PR for the new Port + PR for the New Port Installation Guide Upstream GitLab website @@ -1530,7 +1531,8 @@

          There are more and more machines on the internet that only support IPv6. I manage some of them, - and was regularly hit by missing IPv6 support when building + and was regularly hit by missing IPv6 support when + fetching the distfiles needed for building ports.

          I did some research into the impact of missing IPv6 support @@ -1562,8 +1564,8 @@ - KDE on &os; website - Experimental KDE ports staging area + KDE on &os; Website + Experimental KDE Ports Staging Area KDE on &os; Wiki KDE/&os; Mailing List Development Repository for Integrating KDE Frameworks 5 and Plasma 5 @@ -2537,7 +2539,7 @@ yet sent to upstream). -

          Most of the introduced changes have been committed to HEAD +

          Most of the introduced changes have been committed to head and more are on the way.

          @@ -3133,8 +3135,8 @@
        • Konstantin rewrote the out of memory killer logic, which, in particular, fixed &os; operation on systems without swap, especially systems with very little memory. The latter are - becoming more and more common with popularity of embedded - ARM platforms were &os; runs, but it also affects large + becoming more and more common with the popularity of embedded + ARM platforms where &os; runs, but it also affects large systems which are usually configured without swap. He also finalized and committed the shared page support for the ARMv7 and ARMv8 systems. This allows for a non-executable @@ -3189,7 +3191,7 @@ CUBIEBOARD, and CUBIEBOARD2 arm images.
        • -
        • Deprecated use of MD5 checksums used for verifying +
        • Deprecated the use of MD5 checksums for verifying installation media downloaded from the &os; Project mirrors.
        • @@ -3257,7 +3259,7 @@ support for &os; on x86 as a guest was introduced in version 8, and ARM support is currently being worked on. Support for running &os; as an amd64 Xen host (Dom0) is available in - HEAD.

          + head.

          The x86 work done during this quarter has been focused on rewriting the PVH implementation inside of Xen, into what is @@ -3364,7 +3366,7 @@ directly accessing the timer register. This reduces the overhead of these calls as we no longer need to call into the kernel. This also moves the signal trampoline code away from - the stack allowing for the stack to become non-executable.

          + the stack, allowing for the stack to become non-executable.

          CloudABI support for arm64 was added. This included moving the machine-independent code into a separate file to be shared @@ -3378,7 +3380,7 @@ arm64 have been fixed, resulting in over 17,000 ports building for the architecture.

          -

          The machine-dependent portions of kernel support for +

          The machine-dependent portion of kernel support for single-stepping userland binaries has been started. This will allow debuggers like lldb to step through an application while debugging.

          @@ -3814,7 +3816,7 @@ is activated to continue transmission.

          Additional features of the new sendfile are new - flags that provide an application with extra control over the + flags that provide the application with extra control over the transmitted content. Now it is possible to prevent caching of content in memory, which is useful when it is known that the content is unlikely to be reused any time soon. In such @@ -3833,8 +3835,8 @@ idea of such an asynchronous drop-in replacement was discussed amongst &a.glebius;, &a.scottl;, &a.kib;, &a.adrian;, and Igor Sysoev. The initial prototype was coded by Gleb under the - supervision of Kostik on the VM parts of patch, and under - constant pressure from Igor, who demanded that nginx be + supervision of Kostik on the VM parts of the patch, and under + constant pressure from Igor, who demanded that nginx be capable of running with the new sendfile(2) with no modifications. The prototype demonstrated good performance and stability and quickly went into Netflix production in late @@ -3960,7 +3962,7 @@ -

          The NanoBSD updates target three main areas. First, +

          This quarter's NanoBSD updates target three main areas. First, building a NanoBSD image required root privileges. Second, building for embedded platforms required detailed knowledge of the format required to boot. Third, the exact image sizes @@ -3968,7 +3970,7 @@

          When NanoBSD was written, &os;'s build system required root privileges for the install step and onward. NanoBSD added to - this by creating a md(4) device to construct the + this by creating a md(4) device in which to construct the image. Some configurations of NanoBSD added further to this by creating a chroot in which to cleanly build packages. NanoBSD solves the first problem using the new @@ -4438,7 +4440,7 @@ - + HardenedBSD Website Introducing HardenedBSD's New Binary Updater secadm Beta Published New Package Building Server @@ -4455,7 +4457,7 @@ refactored, but lib32 is now disabled by default.

          We have developed a new binary update utility, - hbsd-update akin to freebsd-update. In + hbsd-update, akin to freebsd-update. In addition to normal OS installs, it can also update jails and ZFS Boot Environments (ZFS BEs). Updates are signed using X.509 certificates.

          From owner-svn-doc-head@freebsd.org Tue Feb 2 04:42:38 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3A38FA985FF; Tue, 2 Feb 2016 04:42:38 +0000 (UTC) (envelope-from bjk@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 09931E04; Tue, 2 Feb 2016 04:42:37 +0000 (UTC) (envelope-from bjk@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u124gbNn064258; Tue, 2 Feb 2016 04:42:37 GMT (envelope-from bjk@FreeBSD.org) Received: (from bjk@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u124gblT064257; Tue, 2 Feb 2016 04:42:37 GMT (envelope-from bjk@FreeBSD.org) Message-Id: <201602020442.u124gblT064257@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bjk set sender to bjk@FreeBSD.org using -f From: Benjamin Kaduk Date: Tue, 2 Feb 2016 04:42:37 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r48140 - head/en_US.ISO8859-1/htdocs/news/status X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Feb 2016 04:42:38 -0000 Author: bjk Date: Tue Feb 2 04:42:36 2016 New Revision: 48140 URL: https://svnweb.freebsd.org/changeset/doc/48140 Log: Remove draft notice from the 2015Q4 report Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Tue Feb 2 04:40:07 2016 (r48139) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Tue Feb 2 04:42:36 2016 (r48140) @@ -15,11 +15,6 @@
          Introduction -

          This is a draft of the October–December 2015 - status report. Please check back after it is finalized, and - an announcement email is sent to the &os;-Announce mailing - list.

          -

          The fourth quarter of 2015 saw a great deal of activity for &os;. This is now the third quarter running for which I can say that this is the largest report yet published! Many thanks to the From owner-svn-doc-head@freebsd.org Tue Feb 2 04:55:50 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B82E9A98A12; Tue, 2 Feb 2016 04:55:50 +0000 (UTC) (envelope-from bjk@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7061B1266; Tue, 2 Feb 2016 04:55:50 +0000 (UTC) (envelope-from bjk@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u124tnG2067431; Tue, 2 Feb 2016 04:55:49 GMT (envelope-from bjk@FreeBSD.org) Received: (from bjk@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u124tnHU067429; Tue, 2 Feb 2016 04:55:49 GMT (envelope-from bjk@FreeBSD.org) Message-Id: <201602020455.u124tnHU067429@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bjk set sender to bjk@FreeBSD.org using -f From: Benjamin Kaduk Date: Tue, 2 Feb 2016 04:55:49 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r48141 - in head: en_US.ISO8859-1/htdocs/news/status share/xml X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Feb 2016 04:55:50 -0000 Author: bjk Date: Tue Feb 2 04:55:49 2016 New Revision: 48141 URL: https://svnweb.freebsd.org/changeset/doc/48141 Log: Publish the 2015Q4 status report Link to it from the main status report page and update the next submission deadline, and add a news entry for the report. The delay in publishing is due to a combination of the large volume of submissions and illness. Modified: head/en_US.ISO8859-1/htdocs/news/status/status.xml head/share/xml/news.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/status.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/status.xml Tue Feb 2 04:42:36 2016 (r48140) +++ head/en_US.ISO8859-1/htdocs/news/status/status.xml Tue Feb 2 04:55:49 2016 (r48141) @@ -13,8 +13,8 @@ -

          Next Quarterly Status Report submissions (October – - December) due: January 7th, 2016

          +

          Next Quarterly Status Report submissions (January – + March) due: April 7th, 2016

          Use the xml generator or download and edit the @@ -58,6 +58,8 @@

          2015

            +
          • October, 2015 - + December, 2015
          • July, 2015 - September, 2015
          • April, 2015 - Modified: head/share/xml/news.xml ============================================================================== --- head/share/xml/news.xml Tue Feb 2 04:42:36 2016 (r48140) +++ head/share/xml/news.xml Tue Feb 2 04:55:49 2016 (r48141) @@ -32,6 +32,22 @@ 2016 + 2 + + + 1 + + + October–December Status Report + +

            The October–December, + 2015 Status Report is now available.

            + + + + + 1 From owner-svn-doc-head@freebsd.org Tue Feb 2 14:54:37 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 473B0A98244; Tue, 2 Feb 2016 14:54:37 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 16F7D628; Tue, 2 Feb 2016 14:54:37 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u12Esaju042509; Tue, 2 Feb 2016 14:54:36 GMT (envelope-from ryusuke@FreeBSD.org) Received: (from ryusuke@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u12Esanx042508; Tue, 2 Feb 2016 14:54:36 GMT (envelope-from ryusuke@FreeBSD.org) Message-Id: <201602021454.u12Esanx042508@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: ryusuke set sender to ryusuke@FreeBSD.org using -f From: Ryusuke SUZUKI Date: Tue, 2 Feb 2016 14:54:36 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r48142 - head/ja_JP.eucJP/share/xml X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Feb 2016 14:54:37 -0000 Author: ryusuke Date: Tue Feb 2 14:54:35 2016 New Revision: 48142 URL: https://svnweb.freebsd.org/changeset/doc/48142 Log: - Merge the following from the English version: r48073 -> r48141 head/ja_JP.eucJP/share/xml/news.xml Modified: head/ja_JP.eucJP/share/xml/news.xml Modified: head/ja_JP.eucJP/share/xml/news.xml ============================================================================== --- head/ja_JP.eucJP/share/xml/news.xml Tue Feb 2 04:55:49 2016 (r48141) +++ head/ja_JP.eucJP/share/xml/news.xml Tue Feb 2 14:54:35 2016 (r48142) @@ -23,7 +23,7 @@ would like to work on. *** $FreeBSD$ - Original revision: r48073 + Original revision: r48141 --> @@ -34,6 +34,23 @@ 2016 + 2 + + + 1 + + + ³«È¯¿ÊĽ¥ì¥Ý¡¼¥È (2015 ǯ 10 ·î – 12 ·î) ¸ø³« + +

            2015 ǯ + 10 ·î – 12 ·î³«È¯¿ÊĽ¥ì¥Ý¡¼¥È + ¤¬¸ø³«¤µ¤ì¤Þ¤·¤¿¡£

            +
            +
            +
            + + 1 From owner-svn-doc-head@freebsd.org Tue Feb 2 15:03:24 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EF052A9858F; Tue, 2 Feb 2016 15:03:24 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C03AAA0E; Tue, 2 Feb 2016 15:03:24 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u12F3N1D045438; Tue, 2 Feb 2016 15:03:23 GMT (envelope-from ryusuke@FreeBSD.org) Received: (from ryusuke@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u12F3NVI045437; Tue, 2 Feb 2016 15:03:23 GMT (envelope-from ryusuke@FreeBSD.org) Message-Id: <201602021503.u12F3NVI045437@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: ryusuke set sender to ryusuke@FreeBSD.org using -f From: Ryusuke SUZUKI Date: Tue, 2 Feb 2016 15:03:23 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r48143 - head/ja_JP.eucJP/htdocs/internal X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Feb 2016 15:03:25 -0000 Author: ryusuke Date: Tue Feb 2 15:03:23 2016 New Revision: 48143 URL: https://svnweb.freebsd.org/changeset/doc/48143 Log: - Merge the following from the English version: r47558 -> r48114 head/ja_JP.eucJP/htdocs/internal/machines.xml Modified: head/ja_JP.eucJP/htdocs/internal/machines.xml Modified: head/ja_JP.eucJP/htdocs/internal/machines.xml ============================================================================== --- head/ja_JP.eucJP/htdocs/internal/machines.xml Tue Feb 2 14:54:35 2016 (r48142) +++ head/ja_JP.eucJP/htdocs/internal/machines.xml Tue Feb 2 15:03:23 2016 (r48143) @@ -4,7 +4,7 @@ ]> - + @@ -90,61 +90,6 @@
          -

          ¥¢¥É¥ß¥Ë¥¹¥È¥ì¡¼¥·¥ç¥óÍѤΠFreeBSD.org ¥Û¥¹¥È

          - -

          °Ê²¼¤Ï¡¢¤µ¤Þ¤¶¤Þ¤Ê¥¢¥É¥ß¥Ë¥¹¥È¥ì¡¼¥·¥ç¥ó¥µ¡¼¥Ó¥¹ÍѤΥ·¥¹¥Æ¥à¤Ç¤¹¡£ -¥·¥¹¥Æ¥à¤Î¤Û¤È¤ó¤É¤Ï¡¢¥¢¥¯¥»¥¹¤¬À©¸Â¤µ¤ì¤Æ¤¤¤Þ¤¹¡£

          - - - - - - - - - - - - - - - - - - - - - - - - - - - -
          ¥Û¥¹¥ÈÌÜŪ
          ftp-masterFTP ¥Þ¥¹¥¿ (¥¹¥Æ¡¼¥¸¥µ¡¼¥Ð)
          skunkworksPerforce ¥µ¡¼¥Ð
          svnSubversion ¥Þ¥¹¥¿¥ê¥Ý¥¸¥È¥ê
          - -

          Ports ¥Ó¥ë¥É¥¯¥é¥¹¥¿

          - -

          ports ¥Ó¥ë¥É¥¯¥é¥¹¥¿¤Ï¡¢¼ç¤Ë Ports Management team (portmgr) ¤¬´ÉÍý¤·¤Æ¤¤¤Þ¤¹¡£

          - - - - - - - - - - - - - - - - - -
          ¥Û¥¹¥ÈÌÜŪ
          beefy[1-8]Package ¥Ó¥ë¥É¥Þ¥·¥ó
          -

          ¥Ï¡¼¥É¥¦¥§¥¢¹½À®

          From owner-svn-doc-head@freebsd.org Tue Feb 2 21:36:02 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C4BACA99FAF; Tue, 2 Feb 2016 21:36:02 +0000 (UTC) (envelope-from jgh@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 91D1A12AC; Tue, 2 Feb 2016 21:36:02 +0000 (UTC) (envelope-from jgh@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u12La18V062299; Tue, 2 Feb 2016 21:36:01 GMT (envelope-from jgh@FreeBSD.org) Received: (from jgh@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u12La1tT062298; Tue, 2 Feb 2016 21:36:01 GMT (envelope-from jgh@FreeBSD.org) Message-Id: <201602022136.u12La1tT062298@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: jgh set sender to jgh@FreeBSD.org using -f From: Jason Helfman Date: Tue, 2 Feb 2016 21:36:01 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r48144 - head/en_US.ISO8859-1/articles/committers-guide X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Feb 2016 21:36:02 -0000 Author: jgh Date: Tue Feb 2 21:36:01 2016 New Revision: 48144 URL: https://svnweb.freebsd.org/changeset/doc/48144 Log: - contributors should be sorted by first name PR: 203708 Submitted by: s3erios@gmail.com Approved by: wblock (mentor) Differential Revision: https://reviews.freebsd.org/D5169 Modified: head/en_US.ISO8859-1/articles/committers-guide/article.xml Modified: head/en_US.ISO8859-1/articles/committers-guide/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/committers-guide/article.xml Tue Feb 2 15:03:23 2016 (r48143) +++ head/en_US.ISO8859-1/articles/committers-guide/article.xml Tue Feb 2 21:36:01 2016 (r48144) @@ -2231,7 +2231,7 @@ freebsd-mfc-after = 2 weeksdoc/head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml — Remove the entry from the Additional Contributors section. Entries - are sorted by last name. + are sorted by first name. From owner-svn-doc-head@freebsd.org Wed Feb 3 16:03:37 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 410CBA9AB79; Wed, 3 Feb 2016 16:03:37 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1038313E4; Wed, 3 Feb 2016 16:03:36 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u13G3are000643; Wed, 3 Feb 2016 16:03:36 GMT (envelope-from madpilot@FreeBSD.org) Received: (from madpilot@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u13G3atI000642; Wed, 3 Feb 2016 16:03:36 GMT (envelope-from madpilot@FreeBSD.org) Message-Id: <201602031603.u13G3atI000642@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: madpilot set sender to madpilot@FreeBSD.org using -f From: Guido Falsi Date: Wed, 3 Feb 2016 16:03:36 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r48145 - head/en_US.ISO8859-1/articles/contributors X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Feb 2016 16:03:37 -0000 Author: madpilot (ports committer) Date: Wed Feb 3 16:03:35 2016 New Revision: 48145 URL: https://svnweb.freebsd.org/changeset/doc/48145 Log: Add Henry Hu for net-im/cutegram. PR: 204350 Modified: head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Modified: head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml ============================================================================== --- head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Tue Feb 2 21:36:01 2016 (r48144) +++ head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Wed Feb 3 16:03:35 2016 (r48145) @@ -3887,6 +3887,11 @@ + Henry Hu + henry.hu.sh@gmail.com + + + Henry Whincup henry@techiebod.com From owner-svn-doc-head@freebsd.org Wed Feb 3 19:44:52 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 43031A9B0CF; Wed, 3 Feb 2016 19:44:52 +0000 (UTC) (envelope-from bhd@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 11CE574B; Wed, 3 Feb 2016 19:44:51 +0000 (UTC) (envelope-from bhd@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u13Jip8f066864; Wed, 3 Feb 2016 19:44:51 GMT (envelope-from bhd@FreeBSD.org) Received: (from bhd@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u13Jip6p066863; Wed, 3 Feb 2016 19:44:51 GMT (envelope-from bhd@FreeBSD.org) Message-Id: <201602031944.u13Jip6p066863@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bhd set sender to bhd@FreeBSD.org using -f From: Bjoern Heidotting Date: Wed, 3 Feb 2016 19:44:51 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r48146 - head/de_DE.ISO8859-1/books/handbook/advanced-networking X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Feb 2016 19:44:52 -0000 Author: bhd Date: Wed Feb 3 19:44:50 2016 New Revision: 48146 URL: https://svnweb.freebsd.org/changeset/doc/48146 Log: Update to r44152: Initial shuffle through Bluetooth chapter to improve flow. Some sections renamed. Flow is now using USB first followed by the various protocols and utilities. Modified: head/de_DE.ISO8859-1/books/handbook/advanced-networking/chapter.xml Modified: head/de_DE.ISO8859-1/books/handbook/advanced-networking/chapter.xml ============================================================================== --- head/de_DE.ISO8859-1/books/handbook/advanced-networking/chapter.xml Wed Feb 3 16:03:35 2016 (r48145) +++ head/de_DE.ISO8859-1/books/handbook/advanced-networking/chapter.xml Wed Feb 3 19:44:50 2016 (r48146) @@ -5,7 +5,7 @@ $FreeBSD$ $FreeBSDde:$ - basiert auf: r44143 + basiert auf: r44152 --> Bluetooth - - Übersicht - Bluetooth ermöglicht die Bildung von persönlichen Netzwerken über drahtlose Verbindungen bei einer maximalen Reichweite von 10 Metern und operiert im unlizensierten @@ -2422,10 +2419,12 @@ freebsdap 00:11:95:c3:0d:ac 1 Die Bluetooth-PC-Card 3CRWB60-A von 3Com verwendet den &man.ng.bt3c.4;-Treiber. Serielle sowie auf UART basierende Bluetooth-Geräte werden von &man.sio.4;, &man.ng.h4.4; - sowie &man.hcseriald.8; unterstützt. Dieses Kapitel - beschreibt die Verwendung von - USB-Bluetooth-Adaptern. - + sowie &man.hcseriald.8; unterstützt. + + Dieses Kapitel beschreibt die Verwendung von + USB-Bluetooth-Adaptern in &os;. Weiterhin + werden verschiedene Bluetooth-Protokolle und Programme + vorgestellt. Die Bluetooth-Unterstützung aktivieren @@ -2471,8 +2470,7 @@ Number of SCO packets: 8 - Das Host Controller Interface - (<acronym>HCI</acronym>) + Suche nach anderen Bluetooth-Geräten HCI @@ -2573,8 +2571,182 @@ Reason: Connection terminated by local h - Das Logical Link Control and Adaptation Protocol - (<acronym>L2CAP</acronym>) + Erstmaliger Verbindungsaufbau zwischen zwei + Bluetooth-Geräten (<foreignphrase>Pairing</foreignphrase>) + + + + Pairing + + + In der Voreinstellung nutzt Bluetooth keine + Authentifizierung, daher kann sich jedes Bluetoothgerät mit + jedem anderen Gerät verbinden. Ein Bluetoothgerät, wie + beispielsweise ein Mobiltelefon, kann jedoch für einen + bestimmten Dienst, etwa eine Einwählverbindung, eine + Authentifizierung anfordern. Bluetooth verwendet zu diesem + Zweck PIN-Codes. Ein + PIN-Code ist ein maximal 16 Zeichen langer + ASCII-String. Damit eine Verbindung zustande kommt, muss auf + beiden Geräten der gleiche PIN-Code + verwendet werden. Nachdem der Code eingegeben wurde, erzeugen + beide Geräte einen link key, + der auf den Geräten gespeichert wird. Beim nächsten + Verbindungsaufbau wird der zuvor erzeugte Link Key verwendet. + Diesen Vorgang bezeichnet man als + Pairing. Geht der Link Key auf + einem Gerät verloren, muss das Pairing wiederholt + werden. + + Der &man.hcsecd.8;-Daemon verarbeitet + Bluetooth-Authentifzierungsanforderungen und wird über die + Datei /etc/bluetooth/hcsecd.conf + konfiguriert. Der folgende Ausschnitt dieser Datei zeigt die + Konfiguration für ein Mobiltelefon, das den + PIN-Code 1234 + verwendet: + + device { + bdaddr 00:80:37:29:19:a4; + name "Pav's T39"; + key nokey; + pin "1234"; + } + + Von der Länge abgesehen, unterliegen + PIN-Codes keinen Einschränkungen. Einige + Geräte, beispielsweise Bluetooth-Headsets, haben einen festen + PIN-Code eingebaut. Die Option + sorgt dafür, dass der + &man.hcsecd.8;-Daemon im Vordergrund läuft. Dadurch kann + der Ablauf einfach verfolgt werden. Stellen Sie das entfernte + Gerät auf receive pairing + und initiieren Sie die Bluetoothverbindung auf dem entfernten + Gerät. Sie erhalten die Meldung, dass Pairing akzeptiert + wurde und der PIN-Code benötigt wird. + Geben Sie den gleichen PIN-Code ein, den + Sie in hcsecd.conf festgelegt haben. Der + Computer und das entfernte Gerät sind nun miteinander + verbunden. Alternativ können Sie das Pairing auch auf dem + entfernten Gerät initiieren. + + &man.hcsecd.8; kann durch das Einfügen + der folgenden Zeile in /etc/rc.conf + beim Systemstart automatisch aktiviert werden: + + hcsecd_enable="YES" + + Es folgt nun eine beispielhafte Ausgabe + des &man.hcsecd.8;-Daemons: + + hcsecd[16484]: Got Link_Key_Request event from 'ubt0hci', remote bdaddr 0:80:37:29:19:a4 +hcsecd[16484]: Found matching entry, remote bdaddr 0:80:37:29:19:a4, name 'Pav's T39', link key doesn't exist +hcsecd[16484]: Sending Link_Key_Negative_Reply to 'ubt0hci' for remote bdaddr 0:80:37:29:19:a4 +hcsecd[16484]: Got PIN_Code_Request event from 'ubt0hci', remote bdaddr 0:80:37:29:19:a4 +hcsecd[16484]: Found matching entry, remote bdaddr 0:80:37:29:19:a4, name 'Pav's T39', PIN code exists +hcsecd[16484]: Sending PIN_Code_Reply to 'ubt0hci' for remote bdaddr 0:80:37:29:19:a4 + + + + Einwahlverbindungen und Netzwerkverbindungen mit + <acronym>PPP</acronym>-Profilen einrichten + + Das + Dial-Up Networking-Profil + (DUN) wird vor allem für Modems und + Mobiltelefone verwendet. Dieses Profil ermöglicht folgende + Szenarien: + + + + Die Verwendung eines Mobiltelefons oder eines + Modems durch einen Computer als drahtloses Modem, um sich + über einen Einwahlprovider mit dem Internet zu verbinden + oder andere Einwahldienste zu benutzen. + + + + Die Verwendung eines Mobiltelefons oder eines + Modems durch einen Computers, um auf Datenabfragen zu + reagieren. + + + + Der Zugriff auf ein Netzwerk über ein + PPP-Profil kann in folgenden Situationen + verwendet werden: + + + + Den LAN-Zugriff für ein einzelnes + Bluetooth-Gerät. + + + + Den LAN-Zugriff für mehrere + Bluetooth-Geräte. + + + + Eine PC-zu-PC-Verbindung unter Verwendung + einer PPP-Verbindung über eine emulierte + serielle Verbindung. + + + + Diese Profile werden unter &os; durch &man.ppp.8; sowie + &man.rfcomm.pppd.8; implementiert - einem Wrapper, der + RFCOMM Bluetooth-Verbindungen unter + PPP nutzbar macht. Bevor ein Profil + verwendet werden kann, muss ein neuer + PPP-Abschnitt in + /etc/ppp/ppp.conf erzeugt werden. + Beispielkonfigurationen zu diesem Thema finden Sie in + &man.rfcomm.pppd.8;. + + Das folgende Beispiel verwendet &man.rfcomm.pppd.8;, um + eine RFCOMM-Verbindung zu einem entfernten + Gerät mit derBD_ADDR 00:80:37:29:19:a4 auf + dem RFCOMM-Kanal DUN + aufzubauen. Die aktuelle + RFCOMM-Kanalnummer erhalten Sie vom + entfernten Gerät über SDP. Es ist auch + möglich, manuell einen RFCOMM-Kanal + festzulegen. In diesem Fall führt &man.rfcomm.pppd.8; keine + SDP-Abfrage durch. Verwenden Sie + &man.sdpcontrol.8;, um die RFCOMM-Kanäle + des entfernten Geräts herauszufinden. + + &prompt.root; rfcomm_pppd -a 00:80:37:29:19:a4 -c -C dun -l rfcomm-dialup + + Der &man.sdpd.8;-Server muss laufen, damit ein Netzzugriff + mit dem PPP LAN-Profil + möglich ist. Außerdem muss für den + LAN-Client ein neuer Eintrag in + /etc/ppp/ppp.conf erzeugt werden. + Beispielkonfigurationen zu diesem Thema finden Sie in + &man.rfcomm.pppd.8;. Danach starten Sie den + RFCOMM PPP-Server + über eine gültige RFCOMM-Kanalnummer. + Der RFCOMM PPP-Server + bindet dadurch den Bluetooth-LAN-Dienst an + den lokalen SDP-Daemon. Das folgende + Beispiel zeigt, wie man den RFCOMM + PPP-Server startet. + + &prompt.root; rfcomm_pppd -s -C 7 -l rfcomm-server + + + + Bluetooth-Protokolle + + Dieser Abschnitt beschreibt die verschiedenen + Bluetooth-Werkzeuge, ihre Funktionen sowie weitere + Programme. + + + Das Logical Link Control and Adaptation Protocol + (<acronym>L2CAP</acronym>) L2CAP @@ -2655,10 +2827,11 @@ c2afe900 c2b53380 1 127 0 Yes Active RFCOMM sockets PCB Recv-Q Send-Q Local address Foreign address Chan DLCI State c2e8bc80 0 250 00:02:72:00:d4:1a 00:07:e0:00:0b:ca 3 6 OPEN - + - - Das <acronym>RFCOMM</acronym>-Protokoll + + Radio Frequency Communication + (<acronym>RFCOMM</acronym>) RFCOMM @@ -2692,86 +2865,9 @@ c2e8bc80 0 250 00:02:72:00:d4:1a Unter &os; ist das RFCOMM-Protokoll im Bluetooth Socket-Layer implementiert. - + - - Erstmaliger Verbindungsaufbau zwischen zwei - Bluetooth-Geräten (<foreignphrase>Pairing</foreignphrase>) - - - - Pairing - - - In der Voreinstellung nutzt Bluetooth keine - Authentifizierung, daher kann sich jedes Bluetoothgerät mit - jedem anderen Gerät verbinden. Ein Bluetoothgerät, wie - beispielsweise ein Mobiltelefon, kann jedoch für einen - bestimmten Dienst, etwa eine Einwählverbindung, eine - Authentifizierung anfordern. Bluetooth verwendet zu diesem - Zweck PIN-Codes. Ein - PIN-Code ist ein maximal 16 Zeichen langer - ASCII-String. Damit eine Verbindung zustande kommt, muss auf - beiden Geräten der gleiche PIN-Code - verwendet werden. Nachdem der Code eingegeben wurde, erzeugen - beide Geräte einen link key, - der auf den Geräten gespeichert wird. Beim nächsten - Verbindungsaufbau wird der zuvor erzeugte Link Key verwendet. - Diesen Vorgang bezeichnet man als - Pairing. Geht der Link Key auf - einem Gerät verloren, muss das Pairing wiederholt - werden. - - Der &man.hcsecd.8;-Daemon verarbeitet - Bluetooth-Authentifzierungsanforderungen und wird über die - Datei /etc/bluetooth/hcsecd.conf - konfiguriert. Der folgende Ausschnitt dieser Datei zeigt die - Konfiguration für ein Mobiltelefon, das den - PIN-Code 1234 - verwendet: - - device { - bdaddr 00:80:37:29:19:a4; - name "Pav's T39"; - key nokey; - pin "1234"; - } - - Von der Länge abgesehen, unterliegen - PIN-Codes keinen Einschränkungen. Einige - Geräte, beispielsweise Bluetooth-Headsets, haben einen festen - PIN-Code eingebaut. Die Option - sorgt dafür, dass der - &man.hcsecd.8;-Daemon im Vordergrund läuft. Dadurch kann - der Ablauf einfach verfolgt werden. Stellen Sie das entfernte - Gerät auf receive pairing - und initiieren Sie die Bluetoothverbindung auf dem entfernten - Gerät. Sie erhalten die Meldung, dass Pairing akzeptiert - wurde und der PIN-Code benötigt wird. - Geben Sie den gleichen PIN-Code ein, den - Sie in hcsecd.conf festgelegt haben. Der - Computer und das entfernte Gerät sind nun miteinander - verbunden. Alternativ können Sie das Pairing auch auf dem - entfernten Gerät initiieren. - - &man.hcsecd.8; kann durch das Einfügen - der folgenden Zeile in /etc/rc.conf - beim Systemstart automatisch aktiviert werden: - - hcsecd_enable="YES" - - Es folgt nun eine beispielhafte Ausgabe - des &man.hcsecd.8;-Daemons: - -hcsecd[16484]: Got Link_Key_Request event from 'ubt0hci', remote bdaddr 0:80:37:29:19:a4 -hcsecd[16484]: Found matching entry, remote bdaddr 0:80:37:29:19:a4, name 'Pav's T39', link key doesn't exist -hcsecd[16484]: Sending Link_Key_Negative_Reply to 'ubt0hci' for remote bdaddr 0:80:37:29:19:a4 -hcsecd[16484]: Got PIN_Code_Request event from 'ubt0hci', remote bdaddr 0:80:37:29:19:a4 -hcsecd[16484]: Found matching entry, remote bdaddr 0:80:37:29:19:a4, name 'Pav's T39', PIN code exists -hcsecd[16484]: Sending PIN_Code_Reply to 'ubt0hci' for remote bdaddr 0:80:37:29:19:a4 - - - + Das Service Discovery Protocol (<acronym>SDP</acronym>) @@ -2877,99 +2973,9 @@ Bluetooth Profile Descriptor List: Kontrollkanal abfragen: &prompt.root; sdpcontrol -l browse - - - - Einwahlverbindungen und Netzwerkverbindungen mit - <acronym>PPP</acronym>-Profilen einrichten - - Das - Dial-Up Networking-Profil - (DUN) wird vor allem für Modems und - Mobiltelefone verwendet. Dieses Profil ermöglicht folgende - Szenarien: - - - - Die Verwendung eines Mobiltelefons oder eines - Modems durch einen Computer als drahtloses Modem, um sich - über einen Einwahlprovider mit dem Internet zu verbinden - oder andere Einwahldienste zu benutzen. - - - - Die Verwendung eines Mobiltelefons oder eines - Modems durch einen Computers, um auf Datenabfragen zu - reagieren. - - - - Der Zugriff auf ein Netzwerk über ein - PPP-Profil kann in folgenden Situationen - verwendet werden: - - - - Den LAN-Zugriff für ein einzelnes - Bluetooth-Gerät. - - - - Den LAN-Zugriff für mehrere - Bluetooth-Geräte. - - - - Eine PC-zu-PC-Verbindung unter Verwendung - einer PPP-Verbindung über eine emulierte - serielle Verbindung. - - - - Diese Profile werden unter &os; durch &man.ppp.8; sowie - &man.rfcomm.pppd.8; implementiert - einem Wrapper, der - RFCOMM Bluetooth-Verbindungen unter - PPP nutzbar macht. Bevor ein Profil - verwendet werden kann, muss ein neuer - PPP-Abschnitt in - /etc/ppp/ppp.conf erzeugt werden. - Beispielkonfigurationen zu diesem Thema finden Sie in - &man.rfcomm.pppd.8;. - - Das folgende Beispiel verwendet &man.rfcomm.pppd.8;, um - eine RFCOMM-Verbindung zu einem entfernten - Gerät mit derBD_ADDR 00:80:37:29:19:a4 auf - dem RFCOMM-Kanal DUN - aufzubauen. Die aktuelle - RFCOMM-Kanalnummer erhalten Sie vom - entfernten Gerät über SDP. Es ist auch - möglich, manuell einen RFCOMM-Kanal - festzulegen. In diesem Fall führt &man.rfcomm.pppd.8; keine - SDP-Abfrage durch. Verwenden Sie - &man.sdpcontrol.8;, um die RFCOMM-Kanäle - des entfernten Geräts herauszufinden. - - &prompt.root; rfcomm_pppd -a 00:80:37:29:19:a4 -c -C dun -l rfcomm-dialup - - Der &man.sdpd.8;-Server muss laufen, damit ein Netzzugriff - mit dem PPP LAN-Profil - möglich ist. Außerdem muss für den - LAN-Client ein neuer Eintrag in - /etc/ppp/ppp.conf erzeugt werden. - Beispielkonfigurationen zu diesem Thema finden Sie in - &man.rfcomm.pppd.8;. Danach starten Sie den - RFCOMM PPP-Server - über eine gültige RFCOMM-Kanalnummer. - Der RFCOMM PPP-Server - bindet dadurch den Bluetooth-LAN-Dienst an - den lokalen SDP-Daemon. Das folgende - Beispiel zeigt, wie man den RFCOMM - PPP-Server startet. - - &prompt.root; rfcomm_pppd -s -C 7 -l rfcomm-server - + - + Das Profil <acronym>OBEX</acronym>-Push (<acronym>OPUSH</acronym>) @@ -3029,10 +3035,10 @@ Success, response: OK, Success (0x20)OBEX-Server gestartet wird: &prompt.root; obexapp -s -C 10 - + - - Das Profil Serial-Port + + Das Serial-Port Profil (<acronym>SPP</acronym>) Das Serial Port Profile (SSP) ermöglicht es Bluetooth-Geräten eine @@ -3059,15 +3065,12 @@ rfcomm_sppd[94692]: Starting on /dev/tty serieller Port verwenden werden. &prompt.root; cu -l ttyp6 + Problembehandlung - - Ein entferntes Gerät kann keine Verbindung - aufbauen - Einige ältere Bluetooth-Geräte unterstützen keinen Rollentausch. Wenn &os; eine neue Verbindung akzeptiert, wird versucht, die Rolle zu tauschen, um zum @@ -3080,19 +3083,14 @@ rfcomm_sppd[94692]: Starting on /dev/tty deaktiviert: &prompt.root; hccontrol -n ubt0hci write_node_role_switch 0 - - - - Bluetooth-Pakete anzeigen Verwenden Sie hcidump, - das Sie als Paket oder über den Port - comms/hcidump installieren können. + das als Paket Port comms/hcidump + verfügbar ist, um Bluetooth-Pakete anzuzeigen. Dieses Programm hat Ähnlichkeiten mit &man.tcpdump.1; und kann zur Anzeige der Bluetooth-Pakete in einem Terminal, oder zur Speicherung von Paketen in einer Datei (Dump) verwendet werden. - From owner-svn-doc-head@freebsd.org Wed Feb 3 19:50:00 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8CD02A9B199; Wed, 3 Feb 2016 19:50:00 +0000 (UTC) (envelope-from bhd@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 54420966; Wed, 3 Feb 2016 19:50:00 +0000 (UTC) (envelope-from bhd@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u13JnxN1067199; Wed, 3 Feb 2016 19:49:59 GMT (envelope-from bhd@FreeBSD.org) Received: (from bhd@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u13Jnxdl067198; Wed, 3 Feb 2016 19:49:59 GMT (envelope-from bhd@FreeBSD.org) Message-Id: <201602031949.u13Jnxdl067198@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bhd set sender to bhd@FreeBSD.org using -f From: Bjoern Heidotting Date: Wed, 3 Feb 2016 19:49:59 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r48147 - head/de_DE.ISO8859-1/books/handbook/network-servers X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Feb 2016 19:50:00 -0000 Author: bhd Date: Wed Feb 3 19:49:59 2016 New Revision: 48147 URL: https://svnweb.freebsd.org/changeset/doc/48147 Log: Update to r42910: Add section describing the new iSCSI stack. This section was translated from the latest r47889. Reviewed by: bcr Differential Revision: https://reviews.freebsd.org/D5170 Modified: head/de_DE.ISO8859-1/books/handbook/network-servers/chapter.xml Modified: head/de_DE.ISO8859-1/books/handbook/network-servers/chapter.xml ============================================================================== --- head/de_DE.ISO8859-1/books/handbook/network-servers/chapter.xml Wed Feb 3 19:44:50 2016 (r48146) +++ head/de_DE.ISO8859-1/books/handbook/network-servers/chapter.xml Wed Feb 3 19:49:59 2016 (r48147) @@ -5,7 +5,7 @@ $FreeBSD$ $FreeBSDde: de-docproj/books/handbook/network-servers/chapter.xml,v 1.103 2011/12/24 15:51:18 bcr Exp $ - basiert auf: r42610 + basiert auf: r42910 --> Netzwerkserver @@ -95,6 +95,11 @@ syslogd, konfiguriert, um Protokolle von anderen Hosts zu akzeptieren. + + + Wissen, wie iSCSI eingerichtet + wird. + Dieses Kapitel setzt folgende Grundkenntnisse voraus: @@ -6432,4 +6437,360 @@ Logging to FILE /var/log/messages + + + + + iSCSI Initiator und Target Konfiguration + + iSCSI bietet die Möglichkeit, + Speicherkapazitäten über ein Netzwerk zu teilen. Im Gegensatz + zu NFS, das auf Dateisystemebene arbeitet, + funktioniert iSCSI auf + Blockgerätebene. + + In der iSCSI-Terminologie wird das + System, das den Speicherplatz zur Verfügung stellt, als + Target bezeichnet. Der Speicherplatz + selbst kann aus einer physischen Festplatte bestehen, oder auch + aus einem Bereich, der mehrere Festplatten, oder nur Teile einer + Festplatte, repräsentiert. Wenn beispielsweise die + Festplatte(n) mit ZFS formatiert ist, kann + ein zvol erstellt werden, welches dann als + iSCSI-Speicher verwendet werden kann. + + Die Clients, die auf den iSCSI-Speicher + zugreifen, werden Initiator genannt. Ihnen + steht der verfügbare Speicher als rohe, nicht formatierte + Festplatte, die auch als LUN bezeichnet wird, + zur Verfügung. Die Gerätedateien für die Festplatten erscheinen + in /dev/ und müssen separat formatiert und + eingehangen werden. + + Seit 10.0-RELEASE enthält &os; einen nativen, + kernelbasierten iSCSI + Target und Initiator. + Dieser Abschnitt beschreibt, wie ein &os;-System als Target oder + Initiator konfiguriert wird. + + + Ein <acronym>iSCSI</acronym>-Target konfigurieren + + + Ein natives iSCSI-Target wird seit + &os; 10.0-RELEASE unterstützt. Um iSCSI + mit älteren Versionen zu benutzen, installieren Sie ein + Target aus der Ports-Sammlung, beispielsweise + net/istgt. Dieses Kapitel beschreibt + nur das native Target. + + + Um ein iSCSI-Target zu konfigurieren, + erstellen Sie die Konfigurationsdatei + /etc/ctl.conf und fügen Sie eine Zeile + in /etc/rc.conf hinzu, um + sicherzustellen, dass &man.ctld.8; automatisch beim Booten + gestartet wird. Starten Sie dann den Daemon. + + Das folgende Beispiel zeigt eine einfache + /etc/ctl.conf. Eine vollständige + Beschreibung dieser Datei und der verfügbaren Optionen finden + Sie in &man.ctl.conf.5;. + + portal-group pg0 { + discovery-auth-group no-authentication + listen 0.0.0.0 + listen [::] +} + +target iqn.2012-06.com.example:target0 { + auth-group no-authentication + portal-group pg0 + + lun 0 { + path /data/target0-0 + size 4G + } +} + + Der erste Eintrag definiert die Portalgruppe + pg0. Portalgruppen legen fest, auf welchen + Netzwerk-Adressen der &man.ctld.8;-Daemon Verbindungen + entgegennehmen wird. Der Eintrag + discovery-auth-group no-authentication + zeigt an, dass jeder Initiator + iSCSI-Targets suchen darf, ohne sich + authentifizieren zu müssen. Die dritte und vierte Zeilen + konfigurieren &man.ctld.8; so, dass er auf allen + IPv4- (listen 0.0.0.0) + und IPv6-Adressen + (listen [::]) auf dem Standard-Port 3260 + lauscht. + + + Es ist nicht zwingend notwendig eine Portalgruppe zu + definieren, da es bereits eine integrierte Portalgruppe namens + default gibt. In diesem Fall ist der + Unterschied zwischen default und + pg0 der, dass bei + default eine Authentifizierung nötig ist, + während bei pg0 die Suche nach Targets + immer erlaubt ist. + + Der zweite Eintrag definiert ein einzelnes Target. Ein + Target hat zwei mögliche Bedeutungen: eine Maschine die + iSCSI bereitstellt, oder eine Gruppe von + LUNs. Dieses Beispiel verwendet die + letztere Bedeutung, wobei + iqn.2012-06.com.example:target0 der Name + des Targets ist. Dieser Name ist nur für Testzwecke geeignet. + Für den tatsächlichen Gebrauch ändern Sie + com.example auf einen echten, rückwärts + geschriebenen Domainnamen. 2012-06 steht + für das Jahr und den Monat, an dem die Domain erworben + wurde. target0 darf einen beliebigen + Wert haben und in der Konfigurationsdatei darf eine beliebige + Anzahl von Targets definiert werden. + + Der Eintrag + auth-group no-authentication erlaubt es + allen Initiatoren sich mit dem angegebenen Target zu verbinden + und portal-group pg0 macht das Target über + die Portalgruppe pg0 erreichbar. + + Die nächste Sektion definiert die LUN. + Jede LUN wird dem Initiator als separate + Platte präsentiert. Für jedes Target können mehrere + LUNs definiert werden. Jede + LUN wird über eine Nummer identifiziert, + wobei LUN 0 verpflichtend ist. Die Zeile + mit dem Pfad path /data/target0-0 definiert + den absoluten Pfad zu der Datei oder des zvols für die + LUN. Der Pfad muss vorhanden sein, bevor + &man.ctld.8; gestartet wird. Die zweite Zeile ist optional + und gibt die Größe der LUN an. Als + nächstes fügen Sie folgende Zeile in + /etc/rc.conf ein, um &man.ctld.8; + automatisch beim Booten zu starten: + + ctld_enable="YES" + + Um &man.ctld.8; jetzt zu starten, geben Sie dieses + Kommando ein: + + &prompt.root; service ctld start + + Der &man.ctld.8;-Daemon liest beim Start + /etc/ctl.conf. Wenn diese Datei nach dem + Starten des Daemons bearbeitet wird, verwenden Sie folgenden + Befehl, damit die Änderungen sofort wirksam werden: + + &prompt.root; service ctld reload + + + Authentifizierung + + Die vorherigen Beispiele sind grundsätzlich unsicher, da + keine Authentifizierung verwendet wird und jedermann vollen + Zugriff auf alle Targets hat. Um für den Zugriff auf die + Targets einen Benutzernamen und ein Passwort vorauszusetzen, + ändern Sie die Konfigurationsdatei wie folgt: + + auth-group ag0 { + chap username1 secretsecret + chap username2 anothersecret +} + +portal-group pg0 { + discovery-auth-group no-authentication + listen 0.0.0.0 + listen [::] +} + +target iqn.2012-06.com.example:target0 { + auth-group ag0 + portal-group pg0 + lun 0 { + path /data/target0-0 + size 4G + } +} + + Die Sektion auth-group definiert die + Benutzernamen und Passwörter. Um sich mit + iqn.2012-06.com.example:target0 zu + verbinden, muss ein Initiator zuerst einen Benutzernamen + und ein Passwort angeben. Eine Suche nach Targets wird + jedoch immer noch ohne Authentifizierung gestattet. Um + eine Authentifizierung zu erfordern, setzen Sie + discovery-auth-group auf eine definierte + auth-group anstelle von + no-autentication. + + In der Regel wird für jeden Initiator ein einzelnes + Target exportiert. In diesem Beispiel wird der Benutzername + und das Passwort direkt im Target-Eintrag festgelegt: + + target iqn.2012-06.com.example:target0 { + portal-group pg0 + chap username1 secretsecret + + lun 0 { + path /data/target0-0 + size 4G + } +} + + + + + Einen <acronym>iSCSI</acronym>-Initiator + konfigurieren + + + Der in dieser Sektion beschriebene + iSCSI-Initiator wird seit &os; + 10.0-RELEASE unterstützt. Lesen Sie &man.iscontrol.8;, wenn + Sie den iSCSI-Initiator mit älteren + Versionen benutzen möchten. + + + Um den Initiator zu verwenden, muss zunächst ein + iSCSI-Daemon gestartet sein. Der + Daemon des Initiators benötigt keine Konfigurationsdatei. Um + den Daemon automatisch beim Booten zu starten, fügen Sie + folgende Zeile in /etc/rc.conf + ein: + + iscsid_enable="YES" + + Um &man.iscsid.8; jetzt zu starten, geben Sie dieses + Kommando ein: + + &prompt.root; service iscsid start + + Die Verbindung mit einem Target kann mit, oder ohne eine + Konfigurationsdatei /etc/iscsi.conf + durchgeführt werden. Dieser Abschnitt beschreibt beide + Möglichkeiten. + + + Verbindung zu einem Target herstellen - ohne + Konfigurationsdatei + + Um einen Initiator mit einem Target zu verbinden, geben + Sie die IP-Adresse des Portals und den + Namen des Ziels an: + + &prompt.root; iscsictl -A -p 10.10.10.10 -t iqn.2012-06.com.example:target0 + + Um zu überprüfen, ob die Verbindung gelungen ist, rufen + Sie iscsictl ohne Argumente auf. Die + Ausgabe sollte in etwa wie folgt aussehen: + + Target name Target portal State +iqn.2012-06.com.example:target0 10.10.10.10 Connected: da0 + + In diesem Beispiel wurde die + iSCSI-Sitzung mit der + LUN /dev/da0 + erfolgreich hergestellt. Wenn das Target + iqn.2012-06.com.example:target0 mehr als + nur eine LUN exportiert, werden mehrere + Gerätedateien in der Ausgabe angezeigt: + + Connected: da0 da1 da2. + + Alle Fehler werden auf die Ausgabe und in die + Systemprotokolle geschrieben. Diese Meldung deutet + beispielsweise darauf hin, dass der &man.iscsid.8;-Daemon + nicht ausgeführt wird: + + Target name Target portal State +iqn.2012-06.com.example:target0 10.10.10.10 Waiting for iscsid(8) + + Die folgende Meldung deutet auf ein Netzwerkproblem hin, + zum Beispiel eine falsche IP-Adresse oder + einen falschen Port: + + Target name Target portal State +iqn.2012-06.com.example:target0 10.10.10.11 Connection refused + + Diese Meldung bedeutet, dass der Name des Targets falsch + angegeben wurde: + + Target name Target portal State +iqn.2012-06.com.example:target0 10.10.10.10 Not found + + Diese Meldung bedeutet, dass das Target eine + Authentifizierung erfordert: + + Target name Target portal State +iqn.2012-06.com.example:target0 10.10.10.10 Authentication failed + + Verwenden Sie diese Syntax, um einen + CHAP-Benutzernamen und ein Passwort + anzugeben: + + &prompt.root; iscsictl -A -p 10.10.10.10 -t iqn.2012-06.com.example:target0 -u user -s secretsecret + + + + Verbindung mit einem Target herstellen - mit + Konfigurationsdatei + + Wenn Sie für die Verbindung eine Konfigurationsdatei + verwenden möchten, erstellen Sie + /etc/iscsi.conf mit etwa folgendem + Inhalt: + + t0 { + TargetAddress = 10.10.10.10 + TargetName = iqn.2012-06.com.example:target0 + AuthMethod = CHAP + chapIName = user + chapSecret = secretsecret +} + + t0 gibt den Namen der Sektion in der + Konfigurationsdatei an. Diser Name wird vom Initiator + benutzt, um zu bestimmen, welche Konfiguration verwendet + werden soll. Die anderen Einträge legen die Parameter fest, + die während der Verbindung verwendet werden. + TargetAddress und + TargetName müssen angegeben werden, + die restlichen sind optional. In diesen Beispiel wird + der CHAP-Benuztername und das Passwort + angegeben. + + Um sich mit einem bestimmten Target zu verbinden, geben + Sie dessen Namen an: + + &prompt.root; iscsictl -An t0 + + Um sich stattdessen mit allen definierten Targets aus + der Konfigurationsdatei zu verbinden, verwenden Sie: + + &prompt.root; iscsictl -Aa + + Damit sich der Initiator automatisch mit allen Targets + aus /etc/iscsi.conf verbindet, fügen + Sie folgendes in /etc/rc.conf + hinzu: + + iscsictl_enable="YES" +iscsictl_flags="-Aa" + + + + From owner-svn-doc-head@freebsd.org Thu Feb 4 01:45:57 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D091A9B059; Thu, 4 Feb 2016 01:45:57 +0000 (UTC) (envelope-from bjk@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C0A1F1859; Thu, 4 Feb 2016 01:45:56 +0000 (UTC) (envelope-from bjk@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u141jti1075595; Thu, 4 Feb 2016 01:45:55 GMT (envelope-from bjk@FreeBSD.org) Received: (from bjk@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u141jtSV075594; Thu, 4 Feb 2016 01:45:55 GMT (envelope-from bjk@FreeBSD.org) Message-Id: <201602040145.u141jtSV075594@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bjk set sender to bjk@FreeBSD.org using -f From: Benjamin Kaduk Date: Thu, 4 Feb 2016 01:45:55 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r48148 - head/en_US.ISO8859-1/htdocs/news/status X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Feb 2016 01:45:57 -0000 Author: bjk Date: Thu Feb 4 01:45:55 2016 New Revision: 48148 URL: https://svnweb.freebsd.org/changeset/doc/48148 Log: A few final tweaks to the 2015Q4 report Mostly surrounding the triage team: emphasize that it is open to the entire community, and remove a non-permanent link. Also deemphasize the importance of "developer", since submission for these reports is open to the entire community. Wordsmith the core report a little to avoid using "lesser" to describe issues. Submitted by: koobs Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Wed Feb 3 19:49:59 2016 (r48147) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Thu Feb 4 01:45:55 2016 (r48148) @@ -17,14 +17,15 @@

          The fourth quarter of 2015 saw a great deal of activity for &os;. This is now the third quarter running for which I can say - that this is the largest report yet published! Many thanks to the - developers who proactively submitted topics and entries — it + that this is the largest report yet published! Many thanks to + everyone who proactively submitted topics and entries — it is great to have more complete coverage of ongoing development for the community to learn about in these reports.

          -

          An experimental new team was formed this quarter to triage - newly-reported bugs and improve the procedures and tooling for - managing bug submissions. Making more effective use of automation +

          An experimental new Triage Team was formed this quarter to + create a new way for community members to participate, + and to improve issue management and productivity in general. + Making more effective use of automation and tooling can help to increase developer productivity and the quality of &os;, just as the adoption of Jenkins and continual integration tooling catches regressions quickly and maintains the @@ -2119,10 +2120,6 @@ href="https://lists.FreeBSD.org/pipermai - - Issue Triage Team's Brainstorming Pad - -

          By the end of the Q4 2015 period, &a.koobs; (koobs@) started an initiative to form an experimental Bugzilla Triage @@ -2643,7 +2640,7 @@ href="https://lists.FreeBSD.org/pipermai

          Beyond these two big questions, Core has handled a number of - lesser items:

          + other items:

          • Core approved the formation of a wiki-admin team to take From owner-svn-doc-head@freebsd.org Thu Feb 4 02:19:14 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0E80BA9B942; Thu, 4 Feb 2016 02:19:14 +0000 (UTC) (envelope-from bjk@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BEB9D3DC; Thu, 4 Feb 2016 02:19:13 +0000 (UTC) (envelope-from bjk@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u142JCxK084283; Thu, 4 Feb 2016 02:19:12 GMT (envelope-from bjk@FreeBSD.org) Received: (from bjk@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u142JCUt084282; Thu, 4 Feb 2016 02:19:12 GMT (envelope-from bjk@FreeBSD.org) Message-Id: <201602040219.u142JCUt084282@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bjk set sender to bjk@FreeBSD.org using -f From: Benjamin Kaduk Date: Thu, 4 Feb 2016 02:19:12 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r48149 - head/en_US.ISO8859-1/htdocs/news/status X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Feb 2016 02:19:14 -0000 Author: bjk Date: Thu Feb 4 02:19:12 2016 New Revision: 48149 URL: https://svnweb.freebsd.org/changeset/doc/48149 Log: Update some more links in the 2015Q4 report Mostly due to overzealous replacement of "freebsd" with "FreeBSD" by one of my helper scripts, but a couple links were dead as submitted, and one snuck by that was missing a description. Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Thu Feb 4 01:45:55 2016 (r48148) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Thu Feb 4 02:19:12 2016 (r48149) @@ -462,7 +462,7 @@ href="https://lists.FreeBSD.org/pipermai - New 1:1-Only Thread Target for &os; + New 1:1-Only Thread Target for &os; @@ -1465,7 +1465,7 @@ href="https://lists.FreeBSD.org/pipermai PR for the New Port - Installation Guide + Installation Guide Upstream GitLab website @@ -1521,7 +1521,7 @@ href="https://lists.FreeBSD.org/pipermai - + Wiki Page @@ -1671,7 +1671,7 @@ href="https://lists.FreeBSD.org/pipermai Ports Collection Landing Page - Contributor's Guide + Contributor's Guide Ports Monitoring Service Ports Management Team Website Portmgr on Facebook @@ -1950,7 +1950,7 @@ href="https://lists.FreeBSD.org/pipermai - Project Information + Project Information Source Code Patch for Review @@ -3241,7 +3241,7 @@ href="https://lists.FreeBSD.org/pipermai &os; PVH DomU Wiki Page &os; PVH Dom0 Wiki Page - &os;/Xen HVMlite Implementation + &os;/Xen HVMlite Implementation @@ -3618,7 +3618,7 @@ href="https://lists.FreeBSD.org/pipermai - MPTCP for &os; Repository + MPTCP for &os; Repository MPTCP for &os; Project Website @@ -4250,7 +4250,7 @@ href="https://lists.FreeBSD.org/pipermai Introduction - &os; binary packages + &os; binary packages Installation How-To Roadmap Commands From owner-svn-doc-head@freebsd.org Thu Feb 4 08:01:54 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BF686A9B17D; Thu, 4 Feb 2016 08:01:54 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8CC8015B4; Thu, 4 Feb 2016 08:01:54 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u1481rts087646; Thu, 4 Feb 2016 08:01:53 GMT (envelope-from eadler@FreeBSD.org) Received: (from eadler@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u1481r5j087645; Thu, 4 Feb 2016 08:01:53 GMT (envelope-from eadler@FreeBSD.org) Message-Id: <201602040801.u1481r5j087645@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: eadler set sender to eadler@FreeBSD.org using -f From: Eitan Adler Date: Thu, 4 Feb 2016 08:01:53 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r48150 - head/en_US.ISO8859-1/articles/explaining-bsd X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Feb 2016 08:01:54 -0000 Author: eadler Date: Thu Feb 4 08:01:53 2016 New Revision: 48150 URL: https://svnweb.freebsd.org/changeset/doc/48150 Log: Remove 15+ yr old reference to the world's busiest FTP server Modified: head/en_US.ISO8859-1/articles/explaining-bsd/article.xml Modified: head/en_US.ISO8859-1/articles/explaining-bsd/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/explaining-bsd/article.xml Thu Feb 4 02:19:12 2016 (r48149) +++ head/en_US.ISO8859-1/articles/explaining-bsd/article.xml Thu Feb 4 08:01:53 2016 (r48150) @@ -31,14 +31,7 @@ In the open source world, the word Linux is almost synonymous with Operating System, but it is not the only - open source &unix; operating system. According - to the Internet - Operating System Counter, as of April 1999 31.3% of the - world's network connected machines run Linux. 14.6% run BSD &unix;. - Some of the world's largest web operations, such as Yahoo!, run BSD. The world's - busiest FTP server of 1999 (now defunct), ftp.cdrom.com, used BSD to - transfer 1.4 TB of data a day. Clearly this is not a niche - market: BSD is a well-kept secret. + open source &unix; operating system. So what is the secret? Why is BSD not better known? This white paper addresses these and other questions. From owner-svn-doc-head@freebsd.org Thu Feb 4 08:05:17 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7297AA9B2E3; Thu, 4 Feb 2016 08:05:17 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 41DED18A8; Thu, 4 Feb 2016 08:05:17 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u1485GLD087789; Thu, 4 Feb 2016 08:05:16 GMT (envelope-from eadler@FreeBSD.org) Received: (from eadler@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u1485G5M087788; Thu, 4 Feb 2016 08:05:16 GMT (envelope-from eadler@FreeBSD.org) Message-Id: <201602040805.u1485G5M087788@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: eadler set sender to eadler@FreeBSD.org using -f From: Eitan Adler Date: Thu, 4 Feb 2016 08:05:16 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r48151 - head/en_US.ISO8859-1/articles/explaining-bsd X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Feb 2016 08:05:17 -0000 Author: eadler Date: Thu Feb 4 08:05:16 2016 New Revision: 48151 URL: https://svnweb.freebsd.org/changeset/doc/48151 Log: - there is more than one variant of Linux - not all BSDs use svn and it isn't core to the BSD model Modified: head/en_US.ISO8859-1/articles/explaining-bsd/article.xml Modified: head/en_US.ISO8859-1/articles/explaining-bsd/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/explaining-bsd/article.xml Thu Feb 4 08:01:53 2016 (r48150) +++ head/en_US.ISO8859-1/articles/explaining-bsd/article.xml Thu Feb 4 08:05:16 2016 (r48151) @@ -58,9 +58,6 @@ The BSD kernel, which handles process scheduling, memory management, symmetric multi-processing (SMP), device drivers, etc. - - Unlike the Linux kernel, there are several different - BSD kernels with differing capabilities. @@ -242,12 +239,10 @@ The BSD kernels are developed and updated following the Open Source development model. Each project maintains a publicly - accessible source tree under - Subversion - (SVN), which contains all source files for the - project, including documentation and other incidental files. SVN - allows users to check out (in other words, to - extract a copy of) any desired version of the system. + accessible source tree + which contains all source files for the + project, including documentation and other incidental files. + Users can obtain a complete copy of any version. A large number of developers worldwide contribute to improvements to BSD. They are divided into three kinds: From owner-svn-doc-head@freebsd.org Thu Feb 4 08:28:58 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6D493A9BB5C; Thu, 4 Feb 2016 08:28:58 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4417B9D0; Thu, 4 Feb 2016 08:28:58 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u148SvAV094087; Thu, 4 Feb 2016 08:28:57 GMT (envelope-from eadler@FreeBSD.org) Received: (from eadler@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u148Sv78094086; Thu, 4 Feb 2016 08:28:57 GMT (envelope-from eadler@FreeBSD.org) Message-Id: <201602040828.u148Sv78094086@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: eadler set sender to eadler@FreeBSD.org using -f From: Eitan Adler Date: Thu, 4 Feb 2016 08:28:57 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r48152 - head/en_US.ISO8859-1/share/xml X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Feb 2016 08:28:58 -0000 Author: eadler Date: Thu Feb 4 08:28:57 2016 New Revision: 48152 URL: https://svnweb.freebsd.org/changeset/doc/48152 Log: Update glossary - remove CVS terms which don't matter anymore - update svn to not explain itself itself in terms of CVS Modified: head/en_US.ISO8859-1/share/xml/glossary.ent Modified: head/en_US.ISO8859-1/share/xml/glossary.ent ============================================================================== --- head/en_US.ISO8859-1/share/xml/glossary.ent Thu Feb 4 08:05:16 2016 (r48151) +++ head/en_US.ISO8859-1/share/xml/glossary.ent Thu Feb 4 08:28:57 2016 (r48152) @@ -315,11 +315,6 @@ - - CVS - - - Carrier Detect CD @@ -375,18 +370,6 @@ - - - Concurrent Versions System - CVS - - A version control system, providing a method of working with and - keeping track of many different revisions of files. CVS provides the - ability to extract, merge and revert individual changes or sets of - changes, and offers the ability to keep track of which changes were - made, by who and for what reason. - - @@ -1346,8 +1329,8 @@ Perforce A source code control product made by - Perforce Software - which is more advanced than CVS. Although not open source, its use + Perforce Software. + Although not open source, its use is free of charge to open-source projects such as &os;. Some &os; developers use a Perforce repository as a staging @@ -1572,12 +1555,10 @@ identification and merging of multiple revisions for each file. RCS consists of many small tools that work together. It lacks some of the features found in more modern revision - control systems, like CVS or Subversion, but it is very simple + control systems, like Git, but it is very simple to install, configure, and start using for a small set of - files. Implementations of RCS can be found on every major - UNIX-like OS. + files. - @@ -1629,32 +1610,6 @@ - - repocopy - - - - - Repository Copy - - A direct copying of files within the CVS repository. - - Without a repocopy, if a file needed to be copied or - moved to another place in the repository, the committer would - run cvs add to put the file in its new - location, and then cvs rm on the old file - if the old copy was being removed. - - The disadvantage of this method is that the history - (i.e. the entries in the CVS logs) of the file would not be - copied to the new location. As the &os; Project considers - this history very useful, a repository copy is often used - instead. This is a process where one of the repository meisters - will copy the files directly within the repository, rather than - using the &man.cvs.1; program. - - - Request For Comments RFC @@ -1794,9 +1749,8 @@ Subversion SVN - Subversion is a version control system, similar to CVS, but - with an expanded feature list. - + Subversion is a version control system + currently used by the &os; project. From owner-svn-doc-head@freebsd.org Thu Feb 4 10:35:38 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1567EA9C174; Thu, 4 Feb 2016 10:35:38 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from smtp-out.elvandar.org (gandalf.elvandar.org [149.210.225.204]) by mx1.freebsd.org (Postfix) with ESMTP id 9F8FB1B16; Thu, 4 Feb 2016 10:35:36 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from gandalf.elvandar.org (localhost [127.0.0.1]) by smtp-out.elvandar.org (Postfix) with ESMTP id B16A72C1DFC; Thu, 4 Feb 2016 11:35:29 +0100 (CET) Received: from smtp-out.elvandar.org ([149.210.225.204]) by gandalf.elvandar.org (gandalf.elvandar.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id q84e6YzLIvF0; Thu, 4 Feb 2016 11:35:26 +0100 (CET) Received: from mail.jr-hosting.nl (mail.jr-hosting.nl [148.251.135.247]) by smtp-out.elvandar.org (Postfix) with ESMTP id 605062C1DFB; Thu, 4 Feb 2016 11:35:26 +0100 (CET) DMARC-Filter: OpenDMARC Filter v1.3.1 smtp-out.elvandar.org 605062C1DFB Authentication-Results: smtp-out.elvandar.org/605062C1DFB; dmarc=none header.from=FreeBSD.org Received: from [10.20.24.249] (gdm.snow.nl [213.154.248.139]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.jr-hosting.nl (Postfix) with ESMTPSA id 56BFFFE6A; Thu, 4 Feb 2016 11:35:10 +0100 (CET) DMARC-Filter: OpenDMARC Filter v1.3.1 mail.jr-hosting.nl 56BFFFE6A Authentication-Results: mail.jr-hosting.nl/56BFFFE6A; dmarc=none header.from=FreeBSD.org Subject: Re: svn commit: r48150 - head/en_US.ISO8859-1/articles/explaining-bsd Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Content-Type: multipart/signed; boundary="Apple-Mail=_AD2C546C-E248-4D30-AFFD-55859ADD3D35"; protocol="application/pgp-signature"; micalg=pgp-sha256 X-Pgp-Agent: GPGMail 2.6b2 From: Remko Lodder In-Reply-To: <201602040801.u1481r5j087645@repo.freebsd.org> Date: Thu, 4 Feb 2016 11:35:09 +0100 Cc: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Message-Id: <1D0251FC-4524-49F3-8B11-A76E787D1270@FreeBSD.org> References: <201602040801.u1481r5j087645@repo.freebsd.org> To: Eitan Adler X-Mailer: Apple Mail (2.3112) X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Feb 2016 10:35:38 -0000 --Apple-Mail=_AD2C546C-E248-4D30-AFFD-55859ADD3D35 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On 04 Feb 2016, at 09:01, Eitan Adler wrote: >=20 > Author: eadler > Date: Thu Feb 4 08:01:53 2016 > New Revision: 48150 > URL: https://svnweb.freebsd.org/changeset/doc/48150 >=20 > Log: > Remove 15+ yr old reference to the world's busiest FTP server >=20 > Modified: > head/en_US.ISO8859-1/articles/explaining-bsd/article.xml >=20 > Modified: head/en_US.ISO8859-1/articles/explaining-bsd/article.xml > = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D > --- head/en_US.ISO8859-1/articles/explaining-bsd/article.xml Thu Feb = 4 02:19:12 2016 (r48149) > +++ head/en_US.ISO8859-1/articles/explaining-bsd/article.xml Thu Feb = 4 08:01:53 2016 (r48150) > @@ -31,14 +31,7 @@ > > In the open source world, the word Linux is = almost > synonymous with Operating System, but it is not = the only > - open source &unix; operating system. According > - to the Internet > - Operating System Counter, as of April 1999 31.3% of the > - world's network connected machines run Linux. 14.6% run BSD = &unix;. > - Some of the world's largest web operations, such as Yahoo!, run BSD. The = world's > - busiest FTP server of 1999 (now defunct), ftp.cdrom.com, used BSD to > - transfer 1.4 TB of data a day. Clearly this is not a niche > - market: BSD is a well-kept secret. > + open source &unix; operating system. >=20 > So what is the secret? Why is BSD not better known? This = white > paper addresses these and other questions. Why remove this? It explains why BSD is used and more specifically it = does not jump from =E2=80=98not the only unix operating system=E2=80=99 = to =E2=80=98so what is the secret, why is bsd not better known=E2=80=99. Pls reconsider. Remko >=20 -- Best regards, Remko Lodder --Apple-Mail=_AD2C546C-E248-4D30-AFFD-55859ADD3D35 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJWsyldAAoJEKjD27JZ84ywKc4P/i4JcfrStz5ifw3zZnnXLDM1 c9CpBa/ywfiQl+/mFHtGqpfx/1i/anUfe9SBLzsp3KiFzZlCqFMycvI8K9pocNL+ mG/T5nzehHdo4oYY81Xpa7qPb1ddMMumypkDFybBOwqn91UPhtooNXbKxgFVhV8Y /CQ6MJGk/wZKNSo/z0cMoZu3cRSHnP87OQO+zejKzbefsLHtWvUmZpdrNqbOuyFd nNDwZQWeaANPVmW+LEvrvsFUZU3b7Vvg8P6hDYlvXgEzJ/Zy5DC6E3xJKy2atwy7 9xqoF2sovF6wy+X09mkevmgBv+f41lNBd6GP89j3yAy75qrCKr0Ojztq1A9eB57c 7Ml33M5kHlFyCIxTBkFiup9hlK7fMN8LyBTT6wuCM8iI9+Bc07qDz2AAcJ8lnG5k EbOKLJH95tj5NvJo9CInljnvWgDpB+TDcpRXSNA4DegG/SteYCeshOXn97eFMKAg /fSIEp4+6WZnjp2rI/yNTIftToJZknyhc0wMdVKuw6eVQP/+Ud+ruzTZDy1KOesq TjacdlWQ1mRPPt1eWyN4BIAcP9qiTth6m+hKoq+EoFEK7VhDNKRdpjcY6dXJmGkA TS0DnPfDE458ILgw+ydgYjnshbf7ifB3jR1Fc+S2yAJINnWnJnIA6fRnocRb3pRU u6sQQe4eVn5ahAdl7t4B =3RR1 -----END PGP SIGNATURE----- --Apple-Mail=_AD2C546C-E248-4D30-AFFD-55859ADD3D35-- From owner-svn-doc-head@freebsd.org Thu Feb 4 10:36:51 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4CE2AA9C1ED; Thu, 4 Feb 2016 10:36:51 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from smtp-out.elvandar.org (smtp-out.elvandar.org [IPv6:2a01:7c8:aaba:ae::2]) by mx1.freebsd.org (Postfix) with ESMTP id 007B51C94; Thu, 4 Feb 2016 10:36:51 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from gandalf.elvandar.org (localhost [127.0.0.1]) by smtp-out.elvandar.org (Postfix) with ESMTP id B4ECD2C1DFC; Thu, 4 Feb 2016 11:36:48 +0100 (CET) Received: from smtp-out.elvandar.org ([149.210.225.204]) by gandalf.elvandar.org (gandalf.elvandar.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id PyOkpK9nxlyh; Thu, 4 Feb 2016 11:36:47 +0100 (CET) Received: from mail.jr-hosting.nl (mail.jr-hosting.nl [148.251.135.247]) by smtp-out.elvandar.org (Postfix) with ESMTP id 0954C2C1DFB; Thu, 4 Feb 2016 11:36:47 +0100 (CET) DMARC-Filter: OpenDMARC Filter v1.3.1 smtp-out.elvandar.org 0954C2C1DFB Authentication-Results: smtp-out.elvandar.org/0954C2C1DFB; dmarc=none header.from=FreeBSD.org Received: from [10.20.24.249] (gdm.snow.nl [213.154.248.139]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.jr-hosting.nl (Postfix) with ESMTPSA id 20637FE74; Thu, 4 Feb 2016 11:36:15 +0100 (CET) DMARC-Filter: OpenDMARC Filter v1.3.1 mail.jr-hosting.nl 20637FE74 Authentication-Results: mail.jr-hosting.nl/20637FE74; dmarc=none header.from=FreeBSD.org Subject: Re: svn commit: r48151 - head/en_US.ISO8859-1/articles/explaining-bsd Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Content-Type: multipart/signed; boundary="Apple-Mail=_01CD04DD-2A4C-4415-9D7A-76E82EE61295"; protocol="application/pgp-signature"; micalg=pgp-sha256 X-Pgp-Agent: GPGMail 2.6b2 From: Remko Lodder In-Reply-To: <201602040805.u1485G5M087788@repo.freebsd.org> Date: Thu, 4 Feb 2016 11:36:15 +0100 Cc: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Message-Id: <5EE95525-E415-4790-8878-FD425C8308CF@FreeBSD.org> References: <201602040805.u1485G5M087788@repo.freebsd.org> To: Eitan Adler X-Mailer: Apple Mail (2.3112) X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Feb 2016 10:36:51 -0000 --Apple-Mail=_01CD04DD-2A4C-4415-9D7A-76E82EE61295 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On 04 Feb 2016, at 09:05, Eitan Adler wrote: >=20 > Author: eadler > Date: Thu Feb 4 08:05:16 2016 > New Revision: 48151 > URL: https://svnweb.freebsd.org/changeset/doc/48151 >=20 > Log: > - there is more than one variant of Linux > - not all BSDs use svn and it isn't core to the BSD model That is incorrect, there is one linux kernel, but there are multiple = distributions. Pls look into that. Remko >=20 > Modified: > head/en_US.ISO8859-1/articles/explaining-bsd/article.xml >=20 > Modified: head/en_US.ISO8859-1/articles/explaining-bsd/article.xml > = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D > --- head/en_US.ISO8859-1/articles/explaining-bsd/article.xml Thu Feb = 4 08:01:53 2016 (r48150) > +++ head/en_US.ISO8859-1/articles/explaining-bsd/article.xml Thu Feb = 4 08:05:16 2016 (r48151) > @@ -58,9 +58,6 @@ > The BSD kernel, which handles process scheduling, memory > management, symmetric multi-processing (SMP), device drivers, > etc. > - > - Unlike the Linux kernel, there are several = different > - BSD kernels with differing capabilities. > >=20 > > @@ -242,12 +239,10 @@ >=20 > The BSD kernels are developed and updated following the = Open > Source development model. Each project maintains a publicly > - accessible source tree under > - Subversion > - (SVN), which contains all source files for the > - project, including documentation and other incidental files. = SVN > - allows users to check out (in other words, to > - extract a copy of) any desired version of the system. > + accessible source tree > + which contains all source files for the > + project, including documentation and other incidental files. > + Users can obtain a complete copy of any version. >=20 > A large number of developers worldwide contribute to = improvements > to BSD. They are divided into three kinds: >=20 -- Best regards, Remko Lodder --Apple-Mail=_01CD04DD-2A4C-4415-9D7A-76E82EE61295 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJWsymfAAoJEKjD27JZ84yw9VkQALYvGE1TYJfKVI6Ke9b91P4J ltodL+674x1hgfVi7lEc0+/G4WCRU1e+X9vz4Qe92Zw3gxmSsi6BosVqpPwHD2ZV Xvdbn15CfCsxIKJL0fBxvmFlSOcohBjz2TRMp6Ihnu/5k4ifLMPxFoEexMCF7dSS ysroUjHxAUFRukzsuhIPYDFWWq4FxU6V9RzolVfq7lhVzE6sZeCb5++jLOlul/Ma ILLo6qEK+pSEgwKkeKIUXC6ZtleHCkrRK3l+gjVjzXTl98JwQDQDEoBqlv2FAn0c 93fVQXsqfnFCPKLM67N9rGOo+bhCMfh596IEOOTWzsDtsZQhKYUxmY8Rk9Y4WqrC W1Ycin6GV+ImPZBaymTaZ8uzfrLiuevcO27+ue9QvpSRb695LteP+eXR9Ifjgejc mEniDzCiFHPPd/gXUu0pMDBYcnPWfDAH07iP551+AhTQWZAH6Q7wOdwW9MdWt3/q Lruqv64pqqkUy/JKYp1PnkAImn9QD/xykdEIQ+8ki/jYPX8ExFXeHBnRewyB8ls9 TzdH68Kikks8lQXDXXRr8oCLC1BMNRBvM5z+5655IdPQdchCMsmSZedfYaDSgQKR wzb96byTuuV/PznTCazT1eNQFBhLNwvB6KFK2dxjhCUUlGfa0mWAZc1u/5gV8sKp V383OhL/OCWXO9IJQPSB =Voqw -----END PGP SIGNATURE----- --Apple-Mail=_01CD04DD-2A4C-4415-9D7A-76E82EE61295-- From owner-svn-doc-head@freebsd.org Thu Feb 4 10:38:25 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1F584A9C282; Thu, 4 Feb 2016 10:38:25 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from smtp-out.elvandar.org (smtp-out.elvandar.org [IPv6:2a01:7c8:aaba:ae::2]) by mx1.freebsd.org (Postfix) with ESMTP id C86EF1E03; Thu, 4 Feb 2016 10:38:24 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from gandalf.elvandar.org (localhost [127.0.0.1]) by smtp-out.elvandar.org (Postfix) with ESMTP id 42B0C2C1DFC; Thu, 4 Feb 2016 11:38:24 +0100 (CET) Received: from smtp-out.elvandar.org ([149.210.225.204]) by gandalf.elvandar.org (gandalf.elvandar.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id LjOW7EgSLLAI; Thu, 4 Feb 2016 11:38:21 +0100 (CET) Received: from mail.jr-hosting.nl (mail.jr-hosting.nl [148.251.135.247]) by smtp-out.elvandar.org (Postfix) with ESMTP id 447CE2C1DFB; Thu, 4 Feb 2016 11:38:21 +0100 (CET) DMARC-Filter: OpenDMARC Filter v1.3.1 smtp-out.elvandar.org 447CE2C1DFB Authentication-Results: smtp-out.elvandar.org/447CE2C1DFB; dmarc=none header.from=FreeBSD.org Received: from [10.20.24.249] (gdm.snow.nl [213.154.248.139]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.jr-hosting.nl (Postfix) with ESMTPSA id D976DFE75; Thu, 4 Feb 2016 11:38:05 +0100 (CET) DMARC-Filter: OpenDMARC Filter v1.3.1 mail.jr-hosting.nl D976DFE75 Authentication-Results: mail.jr-hosting.nl/D976DFE75; dmarc=none header.from=FreeBSD.org Subject: Re: svn commit: r48152 - head/en_US.ISO8859-1/share/xml Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Content-Type: multipart/signed; boundary="Apple-Mail=_CB44212F-75DF-4099-B960-FC87B72F9CE6"; protocol="application/pgp-signature"; micalg=pgp-sha256 X-Pgp-Agent: GPGMail 2.6b2 From: Remko Lodder In-Reply-To: <201602040828.u148Sv78094086@repo.freebsd.org> Date: Thu, 4 Feb 2016 11:38:05 +0100 Cc: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Message-Id: <18A55171-E858-417B-A7F4-F6CC9EA99150@FreeBSD.org> References: <201602040828.u148Sv78094086@repo.freebsd.org> To: Eitan Adler X-Mailer: Apple Mail (2.3112) X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Feb 2016 10:38:25 -0000 --Apple-Mail=_CB44212F-75DF-4099-B960-FC87B72F9CE6 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On 04 Feb 2016, at 09:28, Eitan Adler wrote: >=20 > Author: eadler > Date: Thu Feb 4 08:28:57 2016 > New Revision: 48152 > URL: https://svnweb.freebsd.org/changeset/doc/48152 >=20 > Log: > Update glossary > - remove CVS terms which don't matter anymore > - update svn to not explain itself itself in terms of CVS >=20 > Modified: > head/en_US.ISO8859-1/share/xml/glossary.ent >=20 > Modified: head/en_US.ISO8859-1/share/xml/glossary.ent > = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D > --- head/en_US.ISO8859-1/share/xml/glossary.ent Thu Feb 4 = 08:05:16 2016 (r48151) > +++ head/en_US.ISO8859-1/share/xml/glossary.ent Thu Feb 4 = 08:28:57 2016 (r48152) > @@ -315,11 +315,6 @@ > > >=20 > - > - CVS > - > - > - > > Carrier Detect > CD > @@ -375,18 +370,6 @@ > > > > - > - > - Concurrent Versions System > - CVS > - > - A version control system, providing a method of working = with and > - keeping track of many different revisions of files. CVS = provides the > - ability to extract, merge and revert individual changes or = sets of > - changes, and offers the ability to keep track of which changes = were > - made, by who and for what reason. > - > - > >=20 > > @@ -1346,8 +1329,8 @@ > Perforce > > A source code control product made by > - Perforce = Software > - which is more advanced than CVS. Although not open source, = its use > + Perforce = Software. > + Although not open source, its use > is free of charge to open-source projects such as &os;. >=20 > Some &os; developers use a Perforce repository as a = staging > @@ -1572,12 +1555,10 @@ > identification and merging of multiple revisions for each > file. RCS consists of many small tools that work together. > It lacks some of the features found in more modern revision > - control systems, like CVS or Subversion, but it is very = simple > + control systems, like Git, but it is very simple Like Git, Subversion, Mercurial.. i understand why CVS is removed, but = not SVN. Remko > to install, configure, and start using for a small set of > - files. Implementations of RCS can be found on every major > - UNIX-like OS. > + files. >=20 > - > > > > @@ -1629,32 +1610,6 @@ > > >=20 > - > - repocopy > - > - > - > - > - Repository Copy > - > - A direct copying of files within the CVS = repository. > - > - Without a repocopy, if a file needed to be copied or > - moved to another place in the repository, the committer would > - run cvs add to put the file in its new > - location, and then cvs rm on the old file > - if the old copy was being removed. > - > - The disadvantage of this method is that the history > - (i.e. the entries in the CVS logs) of the file would not be > - copied to the new location. As the &os; Project considers > - this history very useful, a repository copy is often used > - instead. This is a process where one of the repository = meisters > - will copy the files directly within the repository, rather = than > - using the &man.cvs.1; program. > - > - > - > > Request For Comments > RFC > @@ -1794,9 +1749,8 @@ > Subversion > SVN > > - Subversion is a version control system, similar to CVS, = but > - with an expanded feature list. > - > + Subversion is a version control system > + currently used by the &os; project. > > >=20 >=20 -- Best regards, Remko Lodder --Apple-Mail=_CB44212F-75DF-4099-B960-FC87B72F9CE6 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJWsyoNAAoJEKjD27JZ84ywsJQP/imHm7MjVH1/ezVZxJAk0u5C TucREoB5xaXKLECIB3jEpuFG3c2ApW+rz3j8tMSx4srkbyTuOH0WsOXqCWoqJ6Qd WF290mNfws/++hov4IMtWz1XwpuVjlibEh7R0w8bvZ5eO+Yh90vNLNzlQB1dw17Y 3iYODSZeFc0EDX2cp0ewVyKb/4laGa1JYWsn6exAYy2P+RJE71LBPVGr7o9NZmve +jgBnoqcQjqtzee9taCF3jKBb6FjRYJKOLhUSydChLVflkBuLMxcIbYmumOGXeMa NLo3T/A0hUKnIT7tHifgRnQyzwzGgIzfNaiREWg3p/O3AH4IZicdpOvtvM5k5AYc 72WcnkqyWajzFZYaIwb8D0XCw+rGu0aNbbEiX3pduv8HGSRxFLbe9ZEsI1d0RZLr FOvLKJmxiM/S9+5VLizV2sqKprsA38oEe2xhQKxLmoO0frCslrTxO0V1iuxr/LOW pMPMMRnAvqW6/1u0cvaw8vwOD+kA6zQG/itfnO6fhPSNE34JErzWTi34qOKXIqTq hc+TDO9gRw4oYt7OYP0tWqHuWYEN+RMR3TFuCO12ulvKnMvJYHmljGQYckdUd+X2 7mkkxHg99LSxfe5z0Nw0+vifK91FMuQPHf/KpgObmdgPTA/V0Ycgd/kq4vjrFYJn /WSMO33jUbpgmYi59xUY =lDPk -----END PGP SIGNATURE----- --Apple-Mail=_CB44212F-75DF-4099-B960-FC87B72F9CE6-- From owner-svn-doc-head@freebsd.org Thu Feb 4 15:58:36 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 35ADBA9BF77 for ; Thu, 4 Feb 2016 15:58:36 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C52611C3 for ; Thu, 4 Feb 2016 15:58:35 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-wm0-x232.google.com with SMTP id p63so218586041wmp.1 for ; Thu, 04 Feb 2016 07:58:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=UUFlwCYz1SxdrxvO0ovzlPI4KdmnWiagmchL/Ji5rbw=; b=OoixQc/y55xC92/E9yiYdzPck/88mSPyhRvx3VL4P1y2bsFMt18rO7X6r5ABk1sBq+ CH5hOwCXAnWIcPVh5BWVw8h8IniRQ9q0frbAYF5TKXt19R4xr+IEKpB66CAEalxhu57g aaphrELYitMK+wA6yYt0SLDevP9nFaos4ptjw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-type; bh=UUFlwCYz1SxdrxvO0ovzlPI4KdmnWiagmchL/Ji5rbw=; b=IIeEgjoNXRdDJmDmWl3dK0Cu2JlqEccA3UNi6ofTRhpVWpCrHxycL9csNTbzWms5d+ s/cZVFfNvcGQGwl/e9pwKGYWOouA6DN5om5fVgcspfpzDoWH9G2O8id4yIr3DUZsbgvA a6cm3FJRSLr8x1O+5jlUO9E+kKALd4obLTYYM7XYPNnuQqZupR2OV6tV+gZSz09T2mmE /0M1siMh25SSFbDXM66TUUeh308QkDF60rUK3n1v52ryMUoDkLG7wjUjIMkGn/kEJ/rL H7SGLA/EElTUdztJCyAXXIStfiiCIwBuQLquhJ7UDpm+rgJhRY0b5lH5MkurxrjTsRgb jeSA== X-Gm-Message-State: AG10YOQJdlpkmfvZZ7mrdjm2EMpqFFJsebfNaWDz0PcLIqjvksx0laMtc5moqKsfapvdnZ92k3f64q/zlMzIZA== X-Received: by 10.28.223.134 with SMTP id w128mr10648332wmg.69.1454601514203; Thu, 04 Feb 2016 07:58:34 -0800 (PST) MIME-Version: 1.0 Sender: lists@eitanadler.com Received: by 10.28.184.22 with HTTP; Thu, 4 Feb 2016 07:58:04 -0800 (PST) In-Reply-To: <5EE95525-E415-4790-8878-FD425C8308CF@FreeBSD.org> References: <201602040805.u1485G5M087788@repo.freebsd.org> <5EE95525-E415-4790-8878-FD425C8308CF@FreeBSD.org> From: Eitan Adler Date: Thu, 4 Feb 2016 07:58:04 -0800 X-Google-Sender-Auth: bxkUNJAwmvNo5lnkEKu-QL49p3s Message-ID: Subject: Re: svn commit: r48151 - head/en_US.ISO8859-1/articles/explaining-bsd To: Remko Lodder Cc: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Feb 2016 15:58:36 -0000 On 4 February 2016 at 02:36, Remko Lodder wrote: > >> On 04 Feb 2016, at 09:05, Eitan Adler wrote: >> >> Author: eadler >> Date: Thu Feb 4 08:05:16 2016 >> New Revision: 48151 >> URL: https://svnweb.freebsd.org/changeset/doc/48151 >> >> Log: >> - there is more than one variant of Linux >> - not all BSDs use svn and it isn't core to the BSD model > > That is incorrect, there is one linux kernel, but there are multiple distributions. There are many variants of the Linux kernel. Almost no one uses Linus's tree directly. -- Eitan Adler Source, Ports, Doc committer Bugmeister, Ports Security teams From owner-svn-doc-head@freebsd.org Thu Feb 4 16:01:22 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AAC48A7321F for ; Thu, 4 Feb 2016 16:01:22 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 60D277EE for ; Thu, 4 Feb 2016 16:01:22 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-wm0-x22d.google.com with SMTP id g62so11227505wme.0 for ; Thu, 04 Feb 2016 08:01:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=vrh8HFen1tpEXv5NhtxSJsYN5ULGfe8AzyOa1HFb8zg=; b=S+v+MhNwDsbGUsYHDmkuw3DhrHsHO1GtWPIjf4fq9Ul/VrOMZM1atp54menTFdfTWO pzxsah2HhgXmt4JDoQ3hx/hdRqRT4Ko6xMEofm0KWXFclfR6d1dVwfHcWEC5DUDOT6Tn 0zzw04SJwps3dQbKxjaVYh/3SOPr/NvqNGi6A= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=vrh8HFen1tpEXv5NhtxSJsYN5ULGfe8AzyOa1HFb8zg=; b=bWB7JWwvhRJ/0jDyjx1ITsq8+KOAWVDhl75rnDjTo1PZJ+42AfL9n2imWMKyO3yqk0 CAnG/BkCtSX/GuIbgFftwZG4j6W1jhqZmaeMJii5hQPmLjqAuTFSjukm853eXG9ZJkji DS81P6fjl59QIMRhGWvMa+i63a7SnwDUH0PVNshRJhXy1Ubvd/iDQqrEbd2wjlVaNFle oM3MOQb/aTAKbiDQjlGNZhhzwCuOh5GI5/5urNU/78RUz7gE7srr1x1rY947H8DvlFeV QrWqeNkmtAfRMDLYLx0/ZsGeyuQ87xEym23hhl5XWilZhDCH9xQQsAtLs25R2CdWE8i0 5B8A== X-Gm-Message-State: AG10YOS228QlncaJqOs+6F4sb/XqOZlMvoRaFdAucsSD7S+MfWR7zCMszAoUhJ6005jNZ9N+ZtyaVyGLbYBQ2A== X-Received: by 10.28.16.8 with SMTP id 8mr11955133wmq.77.1454601680648; Thu, 04 Feb 2016 08:01:20 -0800 (PST) MIME-Version: 1.0 Sender: lists@eitanadler.com Received: by 10.28.184.22 with HTTP; Thu, 4 Feb 2016 08:00:50 -0800 (PST) In-Reply-To: <1D0251FC-4524-49F3-8B11-A76E787D1270@FreeBSD.org> References: <201602040801.u1481r5j087645@repo.freebsd.org> <1D0251FC-4524-49F3-8B11-A76E787D1270@FreeBSD.org> From: Eitan Adler Date: Thu, 4 Feb 2016 08:00:50 -0800 X-Google-Sender-Auth: CBzl0D-qUuoHEduxi60qkrbKZ1s Message-ID: Subject: Re: svn commit: r48150 - head/en_US.ISO8859-1/articles/explaining-bsd To: Remko Lodder Cc: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Feb 2016 16:01:22 -0000 On 4 February 2016 at 02:35, Remko Lodder wrote: > >> On 04 Feb 2016, at 09:01, Eitan Adler wrote: >> >> Author: eadler >> Date: Thu Feb 4 08:01:53 2016 >> New Revision: 48150 >> URL: https://svnweb.freebsd.org/changeset/doc/48150 >> >> Log: >> Remove 15+ yr old reference to the world's busiest FTP server >> >> Modified: >> head/en_US.ISO8859-1/articles/explaining-bsd/article.xml >> >> Modified: head/en_US.ISO8859-1/articles/explaining-bsd/article.xml >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D >> --- head/en_US.ISO8859-1/articles/explaining-bsd/article.xml Thu Feb 4= 02:19:12 2016 (r48149) >> +++ head/en_US.ISO8859-1/articles/explaining-bsd/article.xml Thu Feb 4= 08:01:53 2016 (r48150) >> @@ -31,14 +31,7 @@ >> >> In the open source world, the word Linux is a= lmost >> synonymous with Operating System, but it is not the= only >> - open source &unix; operating system. According >> - to the Internet >> - Operating System Counter, as of April 1999 31.3% of the >> - world's network connected machines run Linux. 14.6% run BSD &unix= ;. >> - Some of the world's largest web operations, such as Yahoo!, run BSD. The world's >> - busiest FTP server of 1999 (now defunct), ftp.cdrom.com, used BSD to >> - transfer 1.4 TB of data a day. Clearly this is not a niche >> - market: BSD is a well-kept secret. >> + open source &unix; operating system. >> >> So what is the secret? Why is BSD not better known? This w= hite >> paper addresses these and other questions. > > Why remove this? It explains why BSD is used and more specifically it doe= s not jump from =E2=80=98not the only unix operating system=E2=80=99 to =E2= =80=98so what is the secret, why is bsd not better known=E2=80=99. A 15+ yr old reference that talks about transferring 1.4 TB of data a day is hardly impressive. It might be better to reference Netflix or Whatapp now. --=20 Eitan Adler Source, Ports, Doc committer Bugmeister, Ports Security teams From owner-svn-doc-head@freebsd.org Fri Feb 5 00:42:35 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 771F7A9CB02; Fri, 5 Feb 2016 00:42:35 +0000 (UTC) (envelope-from marius@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4B880121C; Fri, 5 Feb 2016 00:42:35 +0000 (UTC) (envelope-from marius@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u150gY44089346; Fri, 5 Feb 2016 00:42:34 GMT (envelope-from marius@FreeBSD.org) Received: (from marius@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u150gYF5089345; Fri, 5 Feb 2016 00:42:34 GMT (envelope-from marius@FreeBSD.org) Message-Id: <201602050042.u150gYF5089345@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: marius set sender to marius@FreeBSD.org using -f From: Marius Strobl Date: Fri, 5 Feb 2016 00:42:34 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r48153 - head/en_US.ISO8859-1/htdocs/releases/10.3R X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Feb 2016 00:42:35 -0000 Author: marius (src,ports committer) Date: Fri Feb 5 00:42:34 2016 New Revision: 48153 URL: https://svnweb.freebsd.org/changeset/doc/48153 Log: Update the 10.3-RELEASE schedule to reflect that 10.3-BETA1 builds have begun. Approved by: re (implicit) Modified: head/en_US.ISO8859-1/htdocs/releases/10.3R/schedule.xml Modified: head/en_US.ISO8859-1/htdocs/releases/10.3R/schedule.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/releases/10.3R/schedule.xml Thu Feb 4 08:28:57 2016 (r48152) +++ head/en_US.ISO8859-1/htdocs/releases/10.3R/schedule.xml Fri Feb 5 00:42:34 2016 (r48153) @@ -83,7 +83,7 @@
          - + From owner-svn-doc-head@freebsd.org Fri Feb 5 09:29:55 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DCECCA76BA6; Fri, 5 Feb 2016 09:29:55 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from smtp-out.elvandar.org (gandalf.elvandar.org [149.210.225.204]) by mx1.freebsd.org (Postfix) with ESMTP id 895991A9E; Fri, 5 Feb 2016 09:29:55 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from gandalf.elvandar.org (localhost [127.0.0.1]) by smtp-out.elvandar.org (Postfix) with ESMTP id 080812C1EC5; Fri, 5 Feb 2016 10:29:54 +0100 (CET) Received: from smtp-out.elvandar.org ([149.210.225.204]) by gandalf.elvandar.org (gandalf.elvandar.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id NTAwcwLGCWIh; Fri, 5 Feb 2016 10:29:52 +0100 (CET) Received: from mail.jr-hosting.nl (mail.jr-hosting.nl [148.251.135.247]) by smtp-out.elvandar.org (Postfix) with ESMTP id 218FF2C1DFB; Fri, 5 Feb 2016 10:29:52 +0100 (CET) DMARC-Filter: OpenDMARC Filter v1.3.1 smtp-out.elvandar.org 218FF2C1DFB Authentication-Results: smtp-out.elvandar.org/218FF2C1DFB; dmarc=none header.from=FreeBSD.org Received: from [IPv6:2001:470:d701::500] (unknown [IPv6:2001:470:d701::500]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.jr-hosting.nl (Postfix) with ESMTPSA id 93E7E2825; Fri, 5 Feb 2016 10:29:36 +0100 (CET) DMARC-Filter: OpenDMARC Filter v1.3.1 mail.jr-hosting.nl 93E7E2825 Authentication-Results: mail.jr-hosting.nl/93E7E2825; dmarc=none header.from=FreeBSD.org Subject: Re: svn commit: r48150 - head/en_US.ISO8859-1/articles/explaining-bsd Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Content-Type: multipart/signed; boundary="Apple-Mail=_D0BEA8EC-22A7-4A90-B2AE-52FA9DF0788F"; protocol="application/pgp-signature"; micalg=pgp-sha256 X-Pgp-Agent: GPGMail 2.6b2 From: Remko Lodder In-Reply-To: Date: Fri, 5 Feb 2016 10:29:35 +0100 Cc: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Message-Id: <376A469D-74FC-4C14-B783-D80B2B34A552@FreeBSD.org> References: <201602040801.u1481r5j087645@repo.freebsd.org> <1D0251FC-4524-49F3-8B11-A76E787D1270@FreeBSD.org> To: Eitan Adler X-Mailer: Apple Mail (2.3112) X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Feb 2016 09:29:56 -0000 --Apple-Mail=_D0BEA8EC-22A7-4A90-B2AE-52FA9DF0788F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On 04 Feb 2016, at 17:00, Eitan Adler wrote: >=20 > On 4 February 2016 at 02:35, Remko Lodder wrote: >>=20 >>> On 04 Feb 2016, at 09:01, Eitan Adler wrote: >>>=20 >>> Author: eadler >>> Date: Thu Feb 4 08:01:53 2016 >>> New Revision: 48150 >>> URL: https://svnweb.freebsd.org/changeset/doc/48150 >>>=20 >>> Log: >>> Remove 15+ yr old reference to the world's busiest FTP server >>>=20 >>> Modified: >>> head/en_US.ISO8859-1/articles/explaining-bsd/article.xml >>>=20 >>> Modified: head/en_US.ISO8859-1/articles/explaining-bsd/article.xml >>> = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D >>> --- head/en_US.ISO8859-1/articles/explaining-bsd/article.xml Thu = Feb 4 02:19:12 2016 (r48149) >>> +++ head/en_US.ISO8859-1/articles/explaining-bsd/article.xml Thu = Feb 4 08:01:53 2016 (r48150) >>> @@ -31,14 +31,7 @@ >>> >>> In the open source world, the word Linux = is almost >>> synonymous with Operating System, but it is not = the only >>> - open source &unix; operating system. According >>> - to the Internet >>> - Operating System Counter, as of April 1999 31.3% of = the >>> - world's network connected machines run Linux. 14.6% run BSD = &unix;. >>> - Some of the world's largest web operations, such as Yahoo!, run BSD. The = world's >>> - busiest FTP server of 1999 (now defunct), ftp.cdrom.com, used BSD to >>> - transfer 1.4 TB of data a day. Clearly this is not a niche >>> - market: BSD is a well-kept secret. >>> + open source &unix; operating system. >>>=20 >>> So what is the secret? Why is BSD not better known? = This white >>> paper addresses these and other questions. >>=20 >> Why remove this? It explains why BSD is used and more specifically it = does not jump from =E2=80=98not the only unix operating system=E2=80=99 = to =E2=80=98so what is the secret, why is bsd not better known=E2=80=99. >=20 > A 15+ yr old reference that talks about transferring 1.4 TB of data a > day is hardly impressive. It might be better to reference Netflix or > Whatapp now. It does not go about =E2=80=98impressive=E2=80=99 or not but for = historical reasons. We can _add_ netflix or whatsapp, but we just should = not remove this because you find it outdated. >=20 > -- > Eitan Adler > Source, Ports, Doc committer > Bugmeister, Ports Security teams >=20 -- Best regards, Remko Lodder --Apple-Mail=_D0BEA8EC-22A7-4A90-B2AE-52FA9DF0788F Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJWtGt/AAoJEKjD27JZ84yw8uIP/3ECGIYjSpibr3WFR7oETEKw sOZw8aeU5xEz9Ir0xkjCPazg3M7Gu849j77UN11la7BF7ublkOBX/8g7dftPpZEL wfmj0Fbjp+AP9x80dM3JxEhGUxJHyDLcaz91lzn/Y7U3WY6cPRx5DitYJvuAf78q bOCKyVK1AvN+mBsPWtQ1ChXVS98g8KEZnktSUTEv1ssvFCQl6hKA6iOi2FQVzKKK L5iD+/7zHkq2C7VK+6dsCXQkCEYCXdqy836To1yEF7kTWJ2Rns6okljVA0YtgekG c8wrQdyELFe2K3DxgBhkFqP15Xn4XVdwHs7rt9SSTZi8/dve/g6fjd4TqlL2wA0B YZIL/Dp7g1nrSu/qAP1npKLL3LCbWm6lQQJOlus1/+WiHIlDoT52n/Bgnr+GNuLO LJcnUDfrRrfQ+siUlGxOnysBWf148JEKesGinxOd2V8hyFWQknOxL991KZA1WpUf f1mP5ASsBRG6+BopVRITFJ0fK0npGZxkYc8DcrrqdnHeroRkx3DONfCKIT5EtfgV VJk+Sed8fN3N6z77P3g+yPOT3fYXVq95ogi2Yj9spn5nfYpYcx6li5WGpt9PXFZ1 i2TrrWoNl8Jlnrcf7sBY6X/r9EcMQYlFFx2BCQLopHmdqYxaoh2kYNunuPqQZPu5 uXhLOLjktbFjwWzGoTk3 =Vzsz -----END PGP SIGNATURE----- --Apple-Mail=_D0BEA8EC-22A7-4A90-B2AE-52FA9DF0788F-- From owner-svn-doc-head@freebsd.org Fri Feb 5 09:30:26 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 70154A76C34; Fri, 5 Feb 2016 09:30:26 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from smtp-out.elvandar.org (smtp-out.elvandar.org [IPv6:2a01:7c8:aaba:ae::2]) by mx1.freebsd.org (Postfix) with ESMTP id 076D01C04; Fri, 5 Feb 2016 09:30:26 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from gandalf.elvandar.org (localhost [127.0.0.1]) by smtp-out.elvandar.org (Postfix) with ESMTP id 6FB4A2C1EC5; Fri, 5 Feb 2016 10:30:25 +0100 (CET) Received: from smtp-out.elvandar.org ([149.210.225.204]) by gandalf.elvandar.org (gandalf.elvandar.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id b_nckgnd9x2c; Fri, 5 Feb 2016 10:30:24 +0100 (CET) Received: from mail.jr-hosting.nl (mail.jr-hosting.nl [148.251.135.247]) by smtp-out.elvandar.org (Postfix) with ESMTP id 97DCD2C1EC7; Fri, 5 Feb 2016 10:30:24 +0100 (CET) DMARC-Filter: OpenDMARC Filter v1.3.1 smtp-out.elvandar.org 97DCD2C1EC7 Authentication-Results: smtp-out.elvandar.org/97DCD2C1EC7; dmarc=none header.from=FreeBSD.org Received: from [IPv6:2001:470:d701::500] (unknown [IPv6:2001:470:d701::500]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.jr-hosting.nl (Postfix) with ESMTPSA id A24D62826; Fri, 5 Feb 2016 10:29:53 +0100 (CET) DMARC-Filter: OpenDMARC Filter v1.3.1 mail.jr-hosting.nl A24D62826 Authentication-Results: mail.jr-hosting.nl/A24D62826; dmarc=none header.from=FreeBSD.org Subject: Re: svn commit: r48151 - head/en_US.ISO8859-1/articles/explaining-bsd Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Content-Type: multipart/signed; boundary="Apple-Mail=_05F1F85F-8A94-426E-B159-78D1C41E5D63"; protocol="application/pgp-signature"; micalg=pgp-sha256 X-Pgp-Agent: GPGMail 2.6b2 From: Remko Lodder In-Reply-To: Date: Fri, 5 Feb 2016 10:29:53 +0100 Cc: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Message-Id: <0B6C0A36-0304-41FF-A498-DCB94EAA93F6@FreeBSD.org> References: <201602040805.u1485G5M087788@repo.freebsd.org> <5EE95525-E415-4790-8878-FD425C8308CF@FreeBSD.org> To: Eitan Adler X-Mailer: Apple Mail (2.3112) X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Feb 2016 09:30:26 -0000 --Apple-Mail=_05F1F85F-8A94-426E-B159-78D1C41E5D63 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On 04 Feb 2016, at 16:58, Eitan Adler wrote: >=20 > On 4 February 2016 at 02:36, Remko Lodder wrote: >>=20 >>> On 04 Feb 2016, at 09:05, Eitan Adler wrote: >>>=20 >>> Author: eadler >>> Date: Thu Feb 4 08:05:16 2016 >>> New Revision: 48151 >>> URL: https://svnweb.freebsd.org/changeset/doc/48151 >>>=20 >>> Log: >>> - there is more than one variant of Linux >>> - not all BSDs use svn and it isn't core to the BSD model >>=20 >> That is incorrect, there is one linux kernel, but there are multiple = distributions. >=20 > There are many variants of the Linux kernel. Almost no one uses > Linus's tree directly. There is one linux, and many distributions. >=20 >=20 > -- > Eitan Adler > Source, Ports, Doc committer > Bugmeister, Ports Security teams >=20 -- Best regards, Remko Lodder --Apple-Mail=_05F1F85F-8A94-426E-B159-78D1C41E5D63 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJWtGuRAAoJEKjD27JZ84yw0wYP/j6sr/pXmeCShAJ6wBvfaZHT RKzTl5v+K23QJBgnjcyjIUTyHQbyr9l8aIo8qHAWmaacKq2qj2r/zBVXI1R3a8kl CXwv6jquyR3xQu0dxiOyL3WN7ROq4N3on0DBzKgMv8lC3QGdxVx/ao4ffusEVjI7 bhpqPppaYewAiYyQZ177OG/m5VNZrV5+LUYwh/AL/joU3qcyP9v9lFGZVikbjGKc ywt00j8xHu+WXSvHzooDix5Vf+D1eyOMCJqUxqdexlfAY5Frj3krpdXMOcBlVtuA ctfBgG26AITFQts10uP58m2mdzlkseTaJFFD8Lvbk3hjSwLF5VQnlfhUZDU0sos+ 4RYSNjfElTx55HOdOZbFrvRqlV/xn4R/EtyEVf7+IhpHMR3o9e5j/Z9u+HAva+o8 WKzuwBc8m8uZxw/DcDSnvFJoftGpcYglDxfuQA+vjwnmiVXeOMw/aAZTCBrlaUxt lK1dsI5LZ58tt3A1yllOv7Ek/9p06/c3qr2xJiDhcH/Qvd7mlD6XfwAuB9Ot3kTk FjPVrh8N0dxRMPIB+eB71GuKdt7JwvfSQxvlFjNL5sEb5X8h5vg1eB7Xyz8SKXaZ 8b7hMlaW9cgm0IWfhlE3meAisWNnmUw22C3OquRJ8ZLzFuzwqy3OrVJZDCufI+o3 6bpdp3QTSNw6yOSlrRwc =i+Wa -----END PGP SIGNATURE----- --Apple-Mail=_05F1F85F-8A94-426E-B159-78D1C41E5D63-- From owner-svn-doc-head@freebsd.org Fri Feb 5 14:51:27 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6BC29A9A6F5 for ; Fri, 5 Feb 2016 14:51:27 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com [IPv6:2607:f8b0:400d:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2EAD2176 for ; Fri, 5 Feb 2016 14:51:27 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk0-x22f.google.com with SMTP id o6so34781545qkc.2 for ; Fri, 05 Feb 2016 06:51:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=kpoaDUyTXbiEHsvdxbK0QKzdznEm8Y13FRJguJMzpM0=; b=zDrJ50ZNj61jUROKFo8FBc2tOXRfv6gijaRzU4aAwpBu4P9B1kGrniJHyj90OktOjP xTrPIj7zf5dLZZwnVkQnTsM7O2LZ3bMsKdcXE1QFIdqF6fjTRmkWBXGt+k6jCM/OA/Th mBW9+tC3ECr+L93+poPUPPSpMEBLPGYXPAvCmVei+fCQkfXJ4qmqyOuOV+FOGw+So2sW BF9vcQULjRXRTISvbtABurIwL40r5EA1ccCQQh7cJMPEhB7A96RwsKfDVNsaTrFBnwOq 16zdwIGrVUevSDBfy1O/tZ8H0S03P+384b1f38FuFmBS2Q7Jq8R1RZn5uwpEpFzAC8Jc AeMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=kpoaDUyTXbiEHsvdxbK0QKzdznEm8Y13FRJguJMzpM0=; b=MOYaZvQoqU6iuJ4DwPPwe6N4E/tFfdoeD9RliyBndDXFfI3ShjDa4oV7/gEbslmE/P GIYjVVntISW5mR1ONlT5fpeN0clT8KJY+XH8ZYUeZ0XQrHfHOhYoQg/m7yImH3sraniV SIany5qEjW8tQHSXPaykNR0UwwzxvS3GYMFsU1+CgR1/L/tkUA6iZFxACp72crsiOouH UgdgcYj9n22FMM62QdXnBz+iTzW1BKNWbXIIsaACRPQ/KoOqjQUqQCicpAuYCRWwQXDh 01Jk3S3wQy1WVSRfiOZ1toBkNo95acQc4PEV7bXRVbzp+MxYnz4T3xAodXSewrDTr5h+ rSHA== X-Gm-Message-State: AG10YORW/SPwyOPywmpN7s7SgQESMUDp7+dD21YAh/fY+KPGcw2zSobmndYU08H2Jr9kKplvpdFKbhE2uObKHg== MIME-Version: 1.0 X-Received: by 10.55.81.87 with SMTP id f84mr16694035qkb.10.1454683885906; Fri, 05 Feb 2016 06:51:25 -0800 (PST) Sender: wlosh@bsdimp.com Received: by 10.140.30.166 with HTTP; Fri, 5 Feb 2016 06:51:25 -0800 (PST) X-Originating-IP: [50.253.99.174] In-Reply-To: <0B6C0A36-0304-41FF-A498-DCB94EAA93F6@FreeBSD.org> References: <201602040805.u1485G5M087788@repo.freebsd.org> <5EE95525-E415-4790-8878-FD425C8308CF@FreeBSD.org> <0B6C0A36-0304-41FF-A498-DCB94EAA93F6@FreeBSD.org> Date: Fri, 5 Feb 2016 07:51:25 -0700 X-Google-Sender-Auth: RLlybVXLPQhPbNlvsPdSYGKe6I4 Message-ID: Subject: Re: svn commit: r48151 - head/en_US.ISO8859-1/articles/explaining-bsd From: Warner Losh To: Remko Lodder Cc: Eitan Adler , doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Feb 2016 14:51:27 -0000 On Fri, Feb 5, 2016 at 2:29 AM, Remko Lodder wrote: > > > On 04 Feb 2016, at 16:58, Eitan Adler wrote: > > > > On 4 February 2016 at 02:36, Remko Lodder wrote: > >> > >>> On 04 Feb 2016, at 09:05, Eitan Adler wrote: > >>> > >>> Author: eadler > >>> Date: Thu Feb 4 08:05:16 2016 > >>> New Revision: 48151 > >>> URL: https://svnweb.freebsd.org/changeset/doc/48151 > >>> > >>> Log: > >>> - there is more than one variant of Linux > >>> - not all BSDs use svn and it isn't core to the BSD model > >> > >> That is incorrect, there is one linux kernel, but there are multiple > distributions. > > > > There are many variants of the Linux kernel. Almost no one uses > > Linus's tree directly. > > There is one linux, and many distributions. > It's all a matter of semantics. You both are right, and also you are both wrong. The 'there's one Linux' mantra has been a mix of both marketing hype and reality. Kinda. It is true there's one mainline kernel that most people fork from. However, the number of people that actually run that kernel stock, without mods, is tiny. Every distribution flavors the kernel, often extensively, as well as other parts of the system. These differences can be quite extensive when you look at it, and it is rare that all the changes make it back into the mainline kernel, though sometimes echos of them do (there's many SoCs that have forked kernels that never get their diffs back into kernel.org: god help you if you have to run on multiple of these from different vendors on a unified kernel version). So Linux really is a thick bush of somewhat similar code bases rather than a single code base that works everywhere. I think from a marketing perspective, we should play these difficulties up and not surrender the marketing point. But that's just me. Warner From owner-svn-doc-head@freebsd.org Fri Feb 5 17:33:13 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 77961A9C6F1 for ; Fri, 5 Feb 2016 17:33:13 +0000 (UTC) (envelope-from bsd-src@helfman.org) Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4939F13D8 for ; Fri, 5 Feb 2016 17:33:13 +0000 (UTC) (envelope-from bsd-src@helfman.org) Received: by mail-io0-x22e.google.com with SMTP id 9so136506139iom.1 for ; Fri, 05 Feb 2016 09:33:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=helfman-org.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=pQ119X5XMu+TVbKvBk59/qVdxFJhCkYCkzt851TskZs=; b=CI8qXhSNZjotZKWQhYKBdTfBAhJ1uO9lgDbX3yceGSz5EqUx8/8uGf2sqU2rBovEXH nCz/3ZyFzA9B3YAsGeyBaA5kt/61GcUFJknhyyo7MahNEM9m3YJpv1ef1xdESoJFURN6 c8tQzzW2+skFhogkMLZQcwqyeAy9L2lgVPfZBs8JzYLpJFrq/G1pjhQ2SbLXvdG2yVdc vyo4p2khEVyxvFHKKu/3Bn3ky2e3W6E+S+lJLPSSXtaMyc7NU48M68VT7nG5Altc3dd/ tNQVie+AXs837dtlo4wfBxZvGnyxFslXrHvDiHzkGhCXuPtCsRizsiUgdViGZeY7xHTo QZIQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=pQ119X5XMu+TVbKvBk59/qVdxFJhCkYCkzt851TskZs=; b=fzOeUz9iBUohnk8RREivREwxrEFVnf/dtY5/keEibbmE2PF3XGAz5xvaJJc5ht6XpC +9WXU/BjJCwdA2laU6qmM40rKLVJu25WxC3s2OzKXt1aKWX9qQSZSYbtCFOxVSU86XQp LSO+ESZHKRZFbH74ZuWopcEQtytqBKJnRjUeb2gL+uYWoed023l4AZi2UUtrUib+OUea ykEHse9RQHgzk5ATE+LPMgxlAA2AV/WqgSdB5e6QgkxUqGv3g0r48C7mipKZY2n+2HdC vyC54u9a3YECEE6YvJEYYVJPp30v0Hr1cMCDYp2WmYSzBpxdVC8o6j8pCXB8oxXe83IW 6Vww== X-Gm-Message-State: AG10YOQA19bVfo3o4+HNfpMensXUcydvNMFcnQ1ezoxPgtPhnAL9w0E2CqXa5oq0QRS6PGV2mqpgVPalQwrB0g== MIME-Version: 1.0 X-Received: by 10.107.136.200 with SMTP id s69mr15885194ioi.120.1454693592368; Fri, 05 Feb 2016 09:33:12 -0800 (PST) Sender: bsd-src@helfman.org Received: by 10.107.142.4 with HTTP; Fri, 5 Feb 2016 09:33:12 -0800 (PST) In-Reply-To: <376A469D-74FC-4C14-B783-D80B2B34A552@FreeBSD.org> References: <201602040801.u1481r5j087645@repo.freebsd.org> <1D0251FC-4524-49F3-8B11-A76E787D1270@FreeBSD.org> <376A469D-74FC-4C14-B783-D80B2B34A552@FreeBSD.org> Date: Fri, 5 Feb 2016 09:33:12 -0800 X-Google-Sender-Auth: Sxq5-t1JQYEcIevqcRtl41yl1JI Message-ID: Subject: Re: svn commit: r48150 - head/en_US.ISO8859-1/articles/explaining-bsd From: Jason Helfman To: Remko Lodder Cc: Eitan Adler , svn-doc-head@freebsd.org, svn-doc-all@freebsd.org, doc-committers@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Feb 2016 17:33:13 -0000 On Fri, Feb 5, 2016 at 1:29 AM, Remko Lodder wrote: > >> On 04 Feb 2016, at 17:00, Eitan Adler wrote: >> >> On 4 February 2016 at 02:35, Remko Lodder wrote: >>> >>>> On 04 Feb 2016, at 09:01, Eitan Adler wrote: >>>> >>>> Author: eadler >>>> Date: Thu Feb 4 08:01:53 2016 >>>> New Revision: 48150 >>>> URL: https://svnweb.freebsd.org/changeset/doc/48150 >>>> >>>> Log: >>>> Remove 15+ yr old reference to the world's busiest FTP server >>>> >>>> Modified: >>>> head/en_US.ISO8859-1/articles/explaining-bsd/article.xml >>>> >>>> Modified: head/en_US.ISO8859-1/articles/explaining-bsd/article.xml >>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D >>>> --- head/en_US.ISO8859-1/articles/explaining-bsd/article.xml Thu Feb = 4 02:19:12 2016 (r48149) >>>> +++ head/en_US.ISO8859-1/articles/explaining-bsd/article.xml Thu Feb = 4 08:01:53 2016 (r48150) >>>> @@ -31,14 +31,7 @@ >>>> >>>> In the open source world, the word Linux is = almost >>>> synonymous with Operating System, but it is not th= e only >>>> - open source &unix; operating system. According >>>> - to the Internet >>>> - Operating System Counter, as of April 1999 31.3% of the >>>> - world's network connected machines run Linux. 14.6% run BSD &un= ix;. >>>> - Some of the world's largest web operations, such as Yahoo!, run BSD. The world's >>>> - busiest FTP server of 1999 (now defunct), ftp.cdrom.com, used BSD to >>>> - transfer 1.4 TB of data a day. Clearly this is not a niche >>>> - market: BSD is a well-kept secret. >>>> + open source &unix; operating system. >>>> >>>> So what is the secret? Why is BSD not better known? This = white >>>> paper addresses these and other questions. >>> >>> Why remove this? It explains why BSD is used and more specifically it d= oes not jump from =E2=80=98not the only unix operating system=E2=80=99 to = =E2=80=98so what is the secret, why is bsd not better known=E2=80=99. >> >> A 15+ yr old reference that talks about transferring 1.4 TB of data a >> day is hardly impressive. It might be better to reference Netflix or >> Whatapp now. > > It does not go about =E2=80=98impressive=E2=80=99 or not but for historic= al reasons. We can _add_ netflix or whatsapp, but we just should not remove= this because you find it outdated. > While I understand the reasoning behind this, and appreciate the mentioning of what could be added, removing an old and potentially relevant entry without adding new content is perceived as an issue. Additionally, have you considered reaching out to our Yahoo! committers, or Yahoo!, to see if they would have any more current statistics so we may update the site (assuming it isn't a small amount, and is comparable to other service providers)? As I recall, this was an opening to listing other service providers that use BSD, and thought it was a nice transition. Regards, Jason --=20 Jason Helfman | FreeBSD Committer jgh@FreeBSD.org | http://people.freebsd.org/~jgh | The Power to Serve From owner-svn-doc-head@freebsd.org Sat Feb 6 03:47:51 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ACBE8A9EE7B for ; Sat, 6 Feb 2016 03:47:51 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4B4DF164D for ; Sat, 6 Feb 2016 03:47:51 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-wm0-x22c.google.com with SMTP id 128so93692086wmz.1 for ; Fri, 05 Feb 2016 19:47:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=IBnmzfA8tntZoJBh9THmMhzyUlb2/u8uQuN2eYJi9/0=; b=TVclHLSfqT1RXjfqe0Vw/Ps8Aon9Me+aruV5tFkcnn4PaJP9TUxeuwKg5iLrMY0v+G GYbxw4UAh0IaMZd8q6T8ecSwOgroAVe9ZeH+hdUfv/1+lF67ws7xzoIzN6RuSZJEL/oc KC5BlKhXc/V8vVh40D4SOh0PJrWYXSoYx47Vw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-type; bh=IBnmzfA8tntZoJBh9THmMhzyUlb2/u8uQuN2eYJi9/0=; b=KJi9o+98fGgx1xMb982l++iOvPb3xw/9BIWBVjXX4C4DDKPzLIwGhi6S6k53XRyh/1 zG9/uf69fylqQ0RvuMSz5YrT4cN7qMTPNn/hDd0vH661XbT5MX9Itfxuz6He+iyDXg4U SzVPMXlka59XHX6CX06DNb622ktK6zX4OtoT5ppiLnIig7XyegDQ/djBZMLqa4dXBkQq /0k48FDTwvPfSpNqQHIRSjbimS7NM9aQUiscAEmkc7Mg8iuMeZD/6sSctUWYz78tHgA3 kdmkZ34cGvcvlSInL9mio6fJU+hXQYa2I3vXeMCpkEByNGORizxmS9bGjNb2wunxbROa UKVw== X-Gm-Message-State: AG10YOSDsIl7M7bkbtJTar6KPYQo3clQc0r0i/3EwBO2Sh9dRc3mj0FJDIqqsIQKxLUzBFJwvh5jzHjtHkrsAw== X-Received: by 10.28.16.8 with SMTP id 8mr20889001wmq.77.1454730469597; Fri, 05 Feb 2016 19:47:49 -0800 (PST) MIME-Version: 1.0 Sender: lists@eitanadler.com Received: by 10.28.184.22 with HTTP; Fri, 5 Feb 2016 19:47:19 -0800 (PST) In-Reply-To: References: <201602040801.u1481r5j087645@repo.freebsd.org> <1D0251FC-4524-49F3-8B11-A76E787D1270@FreeBSD.org> <376A469D-74FC-4C14-B783-D80B2B34A552@FreeBSD.org> From: Eitan Adler Date: Fri, 5 Feb 2016 19:47:19 -0800 X-Google-Sender-Auth: urGqD7IPXCBIWYuh7ZzF8lYUhfk Message-ID: Subject: Re: svn commit: r48150 - head/en_US.ISO8859-1/articles/explaining-bsd To: Jason Helfman Cc: Remko Lodder , svn-doc-head@freebsd.org, svn-doc-all@freebsd.org, doc-committers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Feb 2016 03:47:51 -0000 On 5 February 2016 at 09:33, Jason Helfman wrote: > While I understand the reasoning behind this, and appreciate the > mentioning of what could be added, removing an old and potentially > relevant entry without adding new content is perceived as an issue. > Additionally, have you considered reaching out to our Yahoo! > committers, or Yahoo!, to see if they would have any more current > statistics so we may update the site (assuming it isn't a small > amount, and is comparable to other service providers)? As I recall, > this was an opening to listing other service providers that use BSD, > and thought it was a nice transition. I had some changes from a few months ago when I had time to work on this document. Recently I found them again and committed them again. Should I have time I'll return and try to modernize it some more. It makes sense that just removing content is perceived as an issue but having insanely old content is also an issue. -- Eitan Adler Source, Ports, Doc committer Bugmeister, Ports Security teams
          BETA1 builds begin 5 February 2016-5 February 2016 First beta test snapshot.