From owner-svn-doc-projects@FreeBSD.ORG Mon Jul 8 20:46:28 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2F1667DB; Mon, 8 Jul 2013 20:46:28 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 1EC5A186E; Mon, 8 Jul 2013 20:46:28 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id r68KkSOV011708; Mon, 8 Jul 2013 20:46:28 GMT (envelope-from rene@svn.freebsd.org) Received: (from rene@localhost) by svn.freebsd.org (8.14.7/8.14.5/Submit) id r68KkRUN011702; Mon, 8 Jul 2013 20:46:27 GMT (envelope-from rene@svn.freebsd.org) Message-Id: <201307082046.r68KkRUN011702@svn.freebsd.org> From: Rene Ladan Date: Mon, 8 Jul 2013 20:46:27 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r42196 - in projects/entities: en_US.ISO8859-1/books/fdp-primer/docbook-markup en_US.ISO8859-1/books/handbook/introduction en_US.ISO8859-1/books/porters-handbook en_US.ISO8859-1/htdocs/... X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jul 2013 20:46:28 -0000 Author: rene Date: Mon Jul 8 20:46:26 2013 New Revision: 42196 URL: http://svnweb.freebsd.org/changeset/doc/42196 Log: MFH updated directories up to r42195. Modified: projects/entities/en_US.ISO8859-1/books/fdp-primer/docbook-markup/chapter.xml projects/entities/en_US.ISO8859-1/books/handbook/introduction/chapter.xml projects/entities/en_US.ISO8859-1/books/porters-handbook/book.xml projects/entities/en_US.ISO8859-1/books/porters-handbook/uses.xml projects/entities/en_US.ISO8859-1/htdocs/news/status/report-2013-04-2013-06.xml projects/entities/en_US.ISO8859-1/htdocs/news/status/report-2013-05-devsummit.xml projects/entities/es_ES.ISO8859-1/books/handbook/disks/chapter.xml projects/entities/hu_HU.ISO8859-2/books/handbook/install/chapter.xml projects/entities/it_IT.ISO8859-15/books/handbook/install/chapter.xml projects/entities/ja_JP.eucJP/books/faq/book.xml projects/entities/ja_JP.eucJP/books/handbook/disks/chapter.xml projects/entities/ja_JP.eucJP/books/handbook/introduction/chapter.xml projects/entities/pl_PL.ISO8859-2/books/handbook/install/chapter.xml projects/entities/share/xml/freebsd.sch Directory Properties: projects/entities/en_US.ISO8859-1/ (props changed) projects/entities/es_ES.ISO8859-1/ (props changed) projects/entities/hu_HU.ISO8859-2/ (props changed) projects/entities/it_IT.ISO8859-15/ (props changed) projects/entities/ja_JP.eucJP/ (props changed) projects/entities/pl_PL.ISO8859-2/ (props changed) projects/entities/share/ (props changed) Modified: projects/entities/en_US.ISO8859-1/books/fdp-primer/docbook-markup/chapter.xml ============================================================================== --- projects/entities/en_US.ISO8859-1/books/fdp-primer/docbook-markup/chapter.xml Mon Jul 8 19:21:13 2013 (r42195) +++ projects/entities/en_US.ISO8859-1/books/fdp-primer/docbook-markup/chapter.xml Mon Jul 8 20:46:26 2013 (r42196) @@ -1742,8 +1742,8 @@ This is the file called 'foo2' Images - Image support in the documentation is currently - extremely experimental. The mechanisms described here are + Image support in the documentation is somewhat + experimental. The mechanisms described here are unlikely to change, but that is not guaranteed. Installation of the @@ -1751,11 +1751,11 @@ This is the file called 'foo2' port is required. It is used to convert between the different image formats. This port is not in the textproc/docproj meta - port, it must be installed by hand. + port, it must be installed separately. The best example of what follows in practice is the doc/en_US.ISO8859-1/articles/vm-design/ - document. If the description that follows is unclear, take a + document. If the description that follows is unclear, look at the files in that directory to see how everything hangs together. Experiment with creating different formatted versions of the document to see how the image markup appears @@ -1766,7 +1766,7 @@ This is the file called 'foo2' Image Formats Two image formats are currently supported. Which to - choose will depend on the nature of the image. + use depends on the nature of the image. Images that are primarily vector based, such as network diagrams, time lines, and similar, should be in @@ -1787,8 +1787,8 @@ This is the file called 'foo2' expected that documentation will have a mix of EPS and PNG images. The Makefiles ensure that the correct format - image is chosen depending on the output format that you use - for your documentation. Do not commit the same + image is chosen depending on the output format used. + Do not commit the same image to the repository in two different formats. @@ -1801,11 +1801,49 @@ This is the file called 'foo2' + + Image File Locations + + Image files can be stored in one of several + locations, depending on the document and image: + + + + In the same directory as the document itself, usually + done for articles and small books that keep all their + files in a single directory. + + + + In a subdirectory of the main document. Typically + done when a large book uses separate subdirectories to + organize individual chapters. + + When images are stored in a subdirectory of the + main document directory, the subdirectory name must be + included in their paths in the + Makefile and the + imagedata element. + + + + In a subdirectory of + doc/share/images + named after the document. For example, images for the + Handbook are stored in doc/share/images/books/handbook. + Images that work for multiple translations are stored in + this upper level of the documentation file tree. + Generally, these are images that can be used unchanged in + non-English translations of the document. + + + + Image Markup - The markup for an image is relatively simple. First, - markup a mediaobject. The + Images are included as part of a mediaobject. The mediaobject can contain other, more specific objects. We are concerned with two, the imageobject and the @@ -1814,7 +1852,7 @@ This is the file called 'foo2' Include one imageobject, and two textobject elements. The imageobject will point to the name of the - image file (without the extension). The + image file without the extension. The textobject elements contain information that will be presented to the user as well as, or instead of, the image itself. @@ -1825,10 +1863,10 @@ This is the file called 'foo2' When the reader is viewing the documentation in - HTML. In this case, each image will - need associated alternate text to show the user, typically - while the image is loading, or if they hover the mouse - pointer over the image. + HTML. In this case, each image + needs associated alternate text to show the user, typically + while the image is loading, or if the mouse + pointer is hovered over the image. @@ -1843,24 +1881,23 @@ This is the file called 'foo2' An example will make things easier to understand. Suppose there is an image called fig1.png that is to be included in the document. This image is of a rectangle - with an A inside it. The markup for this would be as - follows. + with an A inside it: - <mediaobject> - <imageobject> - <imagedata fileref="fig1"> - </imageobject> + mediaobject + imageobject + imagedata fileref="fig1" + imageobject - <textobject> - <literallayout class="monospaced">+---------------+ + textobject + literallayout class="monospaced"+---------------+ | A | -+---------------+</literallayout> - </textobject> ++---------------+literallayout + textobject - <textobject> - <phrase>A picture</phrase> - </textobject> -</mediaobject> + textobject + phraseA picturephrase + textobject +mediaobject @@ -1940,7 +1977,7 @@ IMAGES+= fig3.png chapter1/chapter.xml, chapter2/chapter.xml, and chapter3/chapter.xml. If each chapter - has images associated with it, it is suggested to place + has images associated with it, place those images in each chapter's subdirectory (chapter1/, chapter2/, and @@ -1958,14 +1995,14 @@ IMAGES+= fig3.png chapter1/chapter.xml should contain: - <mediaobject> - <imageobject> - <imagedata fileref="chapter1/fig1"> - </imageobject> + mediaobject + imageobject + imagedata fileref="chapter1/fig1" + imageobject … -</mediaobject> +mediaobject @@ -2011,18 +2048,18 @@ IMAGES= chapter1/fig1.png <literal>id</literal> on Chapters and Sections - - Introduction + chapter id="introduction" + titleIntroductiontitle - This is the introduction. It contains a subsection, - which is identified as well. + paraThis is the introduction. It contains a subsection, + which is identified as well.para - - More Details + sect1 id="introduction-moredetails" + titleMore Detailstitle - This is a subsection. - -]]> + paraThis is a subsection.para + sect1 +chapter Use descriptive values for id names. @@ -2043,9 +2080,9 @@ IMAGES= chapter1/fig1.png <sgmltag>anchor</sgmltag> - This paragraph has an embedded - link target in it. It will not - show up in the document.]]> + paraThis paragraph has an embedded + anchor id="para1"link target in it. It will not + show up in the document.para @@ -2066,11 +2103,11 @@ IMAGES= chapter1/fig1.png document that includes the id example shown above: - More information can be found - in . + paraMore information can be found + in xref linkend="introduction".para -More specific information can be found - in .]]> +paraMore specific information can be found + in xref linkend="introduction-moredetails".para The link text will be generated automatically, looking like (emphasized text indicates the @@ -2129,11 +2166,12 @@ IMAGES= chapter1/fig1.png document that includes the id example. - More information can be found in the - sample introduction. + paraMore information can be found in the + link linkend="introduction"sample introductionlink.para -More specific information can be found in the - sample introduction with more details section.]]> +paraMore specific information can be found in the + link linkend="introduction-moredetails"sample introduction with + more detailslink section.para This output will be generated (emphasized text is used to show the @@ -2181,12 +2219,12 @@ IMAGES= chapter1/fig1.png Usage for book links: - Read the SVN - introduction, then pick the nearest mirror from - the list of Subversion - mirror sites.]]> + paraRead the ulink + url="&url.books.handbook;/svn.html#svn-intro"SVN + introductionulink, then pick the nearest mirror from + the list of ulink + url="&url.books.handbook;/subversion-mirrors.html"Subversion + mirror sitesulink.para Appearance: @@ -2199,9 +2237,10 @@ IMAGES= chapter1/fig1.png Usage for article links: - Read this article - about the BSD license, or just the introduction.]]> + paraRead this + ulink url="&url.articles.bsdl-gpl;"article + about the BSD licenseulink, or just the + ulink url="&url.articles.bsdl-gpl;#intro"introductionulink.para Appearance: @@ -2215,9 +2254,8 @@ IMAGES= chapter1/fig1.png Usage: - Of course, you could stop reading this document and - go to the FreeBSD - home page instead.]]> + paraOf course, you could stop reading this document and go to the + ulink url="&url.base;/index.html"FreeBSD home pageulink instead.para Appearance: @@ -2232,10 +2270,10 @@ IMAGES= chapter1/fig1.png Usage: - Wikipedia has an excellent reference on - GUID - Partition Tables.]]> + paraWikipedia has an excellent reference on + ulink + url="http://en.wikipedia.org/wiki/GUID_Partition_Table"GUID + Partition Tablesulink.para Appearance: @@ -2247,9 +2285,9 @@ IMAGES= chapter1/fig1.png The link text can be omitted to show the actual URL: - Wikipedia has an excellent reference on - GUID Partition Tables: .]]> + paraWikipedia has an excellent reference on + GUID Partition Tables: ulink + url="http://en.wikipedia.org/wiki/GUID_Partition_Table"ulink.para Appearance: Modified: projects/entities/en_US.ISO8859-1/books/handbook/introduction/chapter.xml ============================================================================== --- projects/entities/en_US.ISO8859-1/books/handbook/introduction/chapter.xml Mon Jul 8 19:21:13 2013 (r42195) +++ projects/entities/en_US.ISO8859-1/books/handbook/introduction/chapter.xml Mon Jul 8 20:46:26 2013 (r42196) @@ -123,13 +123,6 @@ - &os; is a 32-bit operating - system (64-bit on the &itanium;, - AMD64, and &ultrasparc;) and was designed as such from - the ground up. - - - X Window System Modified: projects/entities/en_US.ISO8859-1/books/porters-handbook/book.xml ============================================================================== --- projects/entities/en_US.ISO8859-1/books/porters-handbook/book.xml Mon Jul 8 19:21:13 2013 (r42195) +++ projects/entities/en_US.ISO8859-1/books/porters-handbook/book.xml Mon Jul 8 20:46:26 2013 (r42196) @@ -5768,11 +5768,11 @@ CMAKE_SOURCE_PATH= ${WRKSRC}/subp Basic Usage If your port requires gettext, set - USES= gettext, and your - port will inherit a dependency on devel/gettext. Other values for - gettext usage are listed in . + USES= gettext, and your port will inherit + a dependency on + devel/gettext. Other + values for gettext usage are listed in + . A rather common case is a port using gettext and configure. @@ -6297,7 +6297,7 @@ USE_XORG= x11 xpm - Updating desktop database + Updating Desktop Database If a port has a MimeType entry in its portname.desktop, @@ -15743,8 +15743,8 @@ Reference: <http://www.freebsd.org/po 901501 November 11, 2012 9.1-STABLE after LIST_PREV() added to queue.h - (rev 242893) and KBI change in USB - serial devices (rev 240659). + (rev 242893) and KBI change in USB + serial devices (rev 240659). @@ -16011,8 +16011,8 @@ Reference: <http://www.freebsd.org/po 1000028 February 13, 2013 - 10-CURRENT after USB moved to the driver structure - requiring a rebuild of all USB modules (rev + 10-CURRENT after USB moved to the driver + structure requiring a rebuild of all USB modules (rev 246759). Modified: projects/entities/en_US.ISO8859-1/books/porters-handbook/uses.xml ============================================================================== --- projects/entities/en_US.ISO8859-1/books/porters-handbook/uses.xml Mon Jul 8 19:21:13 2013 (r42195) +++ projects/entities/en_US.ISO8859-1/books/porters-handbook/uses.xml Mon Jul 8 20:46:26 2013 (r42196) @@ -19,8 +19,9 @@ ada (none) - Depends on an Ada-capable compiler, and - sets CC accordingly. + + Depends on an Ada-capable + compiler, and sets CC accordingly. @@ -39,12 +40,12 @@ charsetfix (none) - Prevents the port from installing charset.alias. - This should be installed only by - converters/libiconv. - CHARSETFIX_MAKEFILEIN can be set to a path relative - to WRKSRC if charset.alias is - not installed by + Prevents the port from installing + charset.alias. This should be installed only + by converters/libiconv. + CHARSETFIX_MAKEFILEIN can be set to a path + relative to WRKSRC if + charset.alias is not installed by WRKSRC/Makefile.in. @@ -64,12 +65,12 @@ Implies that the port uses the update-desktop-database from - devel/desktop-file-utils. - This uses will automatically add a post-install step in such a way - that the port itself still can specify there own post-install step - if needed. It also insert lines into the plist for package - install and removal to run - update-desktop-database. + devel/desktop-file-utils. An + extra post-install step will be run without interfering with any + post-install steps already in the port + Makefile. Lines will be inserted into the + plist to run update-desktop-database on + package install or removal. @@ -85,11 +86,12 @@ gettext (none), lib, build, run - Implies that the port uses devel/gettext in one way or another. By - default, with no arguments or with the lib - argument, implies gettext with build-time and - run-time dependencies, build implies a build-time + Implies that the port uses + devel/gettext in one way or + another. By default, with no arguments or with the + lib argument, implies + gettext with build-time and run-time + dependencies, build implies a build-time dependency, and run implies a run-time dependency. @@ -99,15 +101,16 @@ (none) Implies that the port uses converters/libiconv as build-time and - run-time dependency. - + run-time dependency. ncurses - (none), base, port - Implies that the port uses ncurses, and - causes some useful variables to be set. + (none), base, + port + Implies that the port uses + ncurses, and causes some useful + variables to be set. @@ -151,9 +154,10 @@ readline (none), port - Implies that the port uses readline as - library dependency, and sets CPPFLAGS and - LDFLAGS as necessary. + Implies that the port uses + readline as library dependency, and + sets CPPFLAGS and LDFLAGS as + necessary. @@ -174,23 +178,26 @@ shebangfix (none) - A lot of software uses incorrect locations for script interpreters, - most notably /usr/bin/perl and - /bin/bash. This fixes shebang lines in scripts - listed in SHEBANG_FILES. Currently - Perl, Python, + A lot of software uses incorrect locations for script + interpreters, most notably /usr/bin/perl and + /bin/bash. This fixes shebang lines in + scripts listed in SHEBANG_FILES. Currently + Perl, + Python, Bash, Ruby, - and PHP are supported by default. - To support another interpreter, set SHEBANG_LANG - (for example SHEBANG_LANG=lua), then - lua_OLD_CMD and lua_CMD. + and PHP are supported by default. To + support another interpreter, set SHEBANG_LANG + (for example + SHEBANG_LANG=lua), then + lua_OLD_CMD and + lua_CMD. zenoss (none) - Implies the port uses net-mgmt/zenoss in one way or another, - but largely is used for building zenoss related zenpack + Implies the port uses + net-mgmt/zenoss in one way or + another, but largely is used for building zenoss related zenpack ports. Modified: projects/entities/en_US.ISO8859-1/htdocs/news/status/report-2013-04-2013-06.xml ============================================================================== --- projects/entities/en_US.ISO8859-1/htdocs/news/status/report-2013-04-2013-06.xml Mon Jul 8 19:21:13 2013 (r42195) +++ projects/entities/en_US.ISO8859-1/htdocs/news/status/report-2013-04-2013-06.xml Mon Jul 8 20:46:26 2013 (r42196) @@ -18,7 +18,7 @@

Thanks to all the reporters for the excellent work! This report - contains 14 entries and we hope you enjoy reading it.

+ contains 21 entries and we hope you enjoy reading it.

The deadline for submissions covering between July and September 2013 @@ -67,6 +67,12 @@ Documentation + + event + + Events + + PC-BSD @@ -699,7 +705,7 @@ - + LLDB Debugger Port @@ -751,4 +757,464 @@ system. + + + Native iSCSI Stack + + + + + Edward Tomasz + Napierała + + trasz@FreeBSD.org + + + + + + + + +

The native kernel iSCSI target and initiator project progressed + well over the April to June period. The primary focus was to + introduce support for iSER (iSCSI over RDMA) in both the + initiator and the target. Prerequisite for this was merging + some common parts together and implementing a workaround for the + lack of iSER support in userspace. Apart from that, there were + a myriad of smaller improvements. Such as creating more + user-friendly administration utilities, for example + iscsictl(8) which displays SCSI device nodes for each + iSCSI session. This frees the user from getting the same + information through camcontrol(8). But there are + improvements in logging and manual pages as well.

+ +

Once the iSER support becomes stable, the work will focus on + performance optimizations. The plan is to commit both the new + initiator and target in August to allow shipping them in 10.0. + The project will continue with implementing support for software + iWARP stack (useful mostly for testing and development), SCSI + passthrough and various other improvements.

+ +

This project is being sponsored by the &os; Foundation.

+ + + + Performance optimization. + Merge to &os; head. + + + + + &os; Postmaster Team + + + + + &os; + Postmaster Team + + postmaster@FreeBSD.org + + + + + + +

In the second quarter of 2013, the &os; Postmaster Team has + implemented the following items that may be interest of the + general public:

+ +
    +
  • With help from clusteradm, found that + unbound (the resolver used on mx1 and + mx2) is configured to perform DNSSEC validation which + implies that if a signed zone fails validation, + unbound refuses to use the information. This had + caused one person to be unable to exchange email with + &os;.org until the zone signatures were + refreshed.
    • + +
  • Created the freebsd-dtrace mailing list per George + Neville-Neil.
    • + +
  • Resurrected the freebsd-testing mailing list per + Garrett Cooper.
    • + +
  • Created the freebsd-tex mailing list per Hiroki + Sato.
    • + +
  • In response to another comment that our message rejection + message was unclear in the case that greylisting was the + reason, re-worded that message.
    • + +
  • Augmented the allowable MIME types for secteam with + the following to permit sending encrypted messages: + +
      +
    • application/pgp-encrypted
      • +
    • application/pkcs7-encrypted
      • +
    • application/x-pkcs7-encrypted
      • +
    • multipart/encrypted
      • +
    +
    • + +
  • Initiated de-orbit for freebsd-mozilla in favor of + freebsd-gecko.
    • +
+ + + + + Capsicum + + + + + Pawel Jakub + Dawidek + + pjd@FreeBSD.org + + + + + Capsicum + Mailing List + + cl-capsicum-discuss@lists.cam.ac.uk + + + + + + + + + +

Capsicum (lightweight OS capability and sandbox framework) is + being actively worked on. In the last few months the following + tasks have been completed:

+ +
    +
  • Committed Capsicum overhaul to &os; head (r247602). + This allows to use capability rights in more places, simplifies + kernel code and implements ability to limit ioctl(2) + and fcntl(2) system calls.
    • + +
  • hastd(8) is now using Capsicum for sandboxing, as + whitelisting ioctls is possible (r248297).
    • + +
  • auditdistd(8) is now using Capsicum for sandboxing, + as it is now possible to setup append-only restriction on file + descriptor (available in Perforce).
    • + +
  • Implemented connectat(2) and bindat(2) + system calls for UNIX domain sockets that are allowed in + capability mode (r247667).
    • + +
  • Implemented chflagsat(2) system call + (r248599).
    • + +
  • Revised the Casper daemon for application capabilities.
    • + +
  • Implemented libcapsicum for application + capabilities.
    • + +
  • Implemented various Casper services to be able to use more + functionality within a sandbox: system.dns, + system.pwd, system.grp, + system.random, system.filesystem, + system.socket, system.sysctl.
    • + +
  • Implemented Capsicum sandboxing for kdump(1) (from + r251073 to r251167). The version in Perforce also supports + sandboxing for the -r flag, using Casper + services.
    • + +
  • Implemented Capsicum sandboxing for dhclient(8) + (from r252612 to r252697).
    • + +
  • Implemented Capsicum sandboxing for tcpdump(8) + (available in Perforce).
    • + +
  • Implemented Capsicum sandboxing for libmagic(3) + (available in Perforce).
    • + +
  • Implemented the libnv library for name/value pairs + handling in the hope of wider adaptation across &os;.
    • +
+ +

For Capsicum-based sandboxing in the &os; base system, the + commits referenced above and the provided code aim to serve as + examples. We would like to see more &os; tools to be sandboxed + — every tool that can parse data from untrusted sources, + for example. This requires deep understanding of how the tool + in question works, not necessarily only Capsicum.

+ +

This work is being sponsored by the &os; Foundation.

+ + + + Get involved, make the Internet finally(!) a secure place. + Contact us at the cl-capsicum-discuss mailing list, + where we can provide guidelines on how to do sandboxing + properly. The fame is there, waiting. + + + + + Xfce/&os; + + + + + &os; Xfce Team + + xfce@FreeBSD.org + + + + + + + + +

The &os; Xfce Team has updated its ports to the latest stable + releases, especially:

+ +
    +
  • Core (mostly bugfixes and translation updates):
    • + +
      +
    • deskutils/xfce4-tumbler (0.1.29)
      • +
    • x11-wm/xfce4-panel (4.10.1)
      • +
    • sysutils/xfce4-settings (4.10.1)
      • +
    • x11-wm/xfce4-session (4.10.1)
      • +
    • sysutils/garcon (0.2.1)
      • +
    • x11/libxfce4util (4.10.1)
      • +
    • x11-wm/xfce4-wm (4.10.1)
      • +
    + +
  • Applications:
    • + +
      +
    • multimedia/xfce4-parole (0.5.1)
      • +
    • www/midori (0.5.2)
      • +
    • deskutils/xfce4-notifyd (0.2.4)
      • +
    • misc/xfce4-appfinder (4.10.1)
      • +
    • x11/xfce4-terminal (0.6.2)
      • +
    • x11-fm/thunar (1.6.3)
      • +
    + +
  • Panel plugins:
    • + +
      +
    • deskutils/xfce4-xkb-plugin (0.5.6)
      • +
    • textproc/xfce4-dict-plugin (0.7.0)
      • +
    • x11-clocks/xfce4-timer-plugin (1.5.0)
      • +
    • x11/xfce4-embed-plugin (new)
      • +
    + +
  • Thunar plugins:
    • + +
      +
    • audio/thunar-media-tags-plugin (0.2.1)
      • +
    • archivers/thunar-archive-plugin (0.3.1)
      • +
    + +
  • x11/xfce4-embed-plugin can integrate any + application window into the Xfce panel.
    • + +
  • A new plugin is also available which monitors and displays earthquakes, + it is called xfce4-equake-plugin.
    • +
+ + + + Fix CPU issue with textproc/xfce4-dict-plugin (bug #10103). + + Investigate why midori-gtk3 crashes too often. + (The port is finished, but some libraries are not present by + default in ports tree). + + Fix x11-themes/gtk-xfce-engine with Gtk+ >=3.6. + + + + + &os; Security Team + + + + + &os; Security Team + + secteam@FreeBSD.org + + + + + + +

On April 15th Dag-Erling Smørgrav and Xin Li took over + as security officers for the &os; Project, and the team welcomed + Qing Li back in the team in June. This report briefly + summarizes the work of the Security Team from April until the + end of June.

+ +

The Security Team has released the following advisories:

+ +
    +
  • FreeBSD-SA-13:05.nfsserver: Insufficient input + validation in the NFS server (nfsd(8)), reported by + Adam Nowacki.
    • + +
  • FreeBSD-SA-13:06.mmap: Privilege escalation via + mmap(), reported by Konstantin Belousov.
    • + +
  • FreeBSD-EN-13:02.vtnet: vtnet(4) + network interface issue on QEMU 1.4.0 and later in 8.4-RELEASE, + reported by Julian Stecklina.
    • + +
  • FreeBSD-EN-13:01.fxp: dhclient(8) utility + issue on fxp(4) network interface in 8.4-RELEASE, + reported by Michael L. Squires.
    • +
+ +

Per request of Baptiste Daroussin, the Security Team has also + reviewed the source code of Poudriere, the port build and test + system which is planned to be used for producing pkg(8) + ("new-style") packages on the &os; cluster.

+ + + + + BSD-Day 2013 + + + + + Gábor + Páli + + pgj@FreeBSD.org + + + + + BSD-Day 2013 web site + YouTube playlist of talks + Event photo album + + + +

The BSD-Day is a now recurring excuse for BSD developers and + users to meet up in person, share some beers and talk about what + they are working on these days. There was a detour this year to + visit the beautiful city of Naples of Italy, the home of pizza. + Fortunately, the event has again gained support from numerous + and generous sponsors, such as the &os; Foundation, the EMC + Corporation, iXsystems, FreeBSDMall, BSD Magazine, and many + others which enabled us to cover the costs of travel and + accommodation for the speakers. We are really grateful for + this!

+ +

Similarly to the previous years, the whole event started with a + common dinner in the downtown (somewhere around the Ireland + Irish Pub) on Friday which suddenly turned into a do-it-yourself + pizza-fest. Then it was followed by the Saturday event at the + Institute of Biostructures and Bioimaging. There we had a lot + of attendees for the associated BSDA exam in the morning — + 8 persons! The event itself had many interesting topics as + well, for example moving MCLinker into the BSD world, + organization and culture of the &os; Project, the new + callout(9) framework, building and testing ports with + Poudriere and Tinderbox, &os; in the embedded space, or building + reliable VPN networks with OpenBSD. See the links in the report + for more.

+ + + + + xorg on &os; + + + + x11@FreeBSD.org + + + + + Niclas + Zeising + + zeising@FreeBSD.org + + + + + Koop + Mast + + kwm@FreeBSD.org + + + + + + + + + +

During the beginning of this quarter, work focused on making *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***