FreeBSD 10.0-RELEASE Errata

The FreeBSD Project

FreeBSD 10.0-RELEASE Errata

The FreeBSD Project

FreeBSD is a registered trademark of the FreeBSD Foundation.

Intel, Celeron, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or registered @@ -13,7 +13,7 @@ as trademarks. Where those designations appear in this document, and the FreeBSD Project was aware of the trademark claim, the designations have been followed by the “™” or the - “�” symbol.

Last modified on 2014-09-09 by gjb.

Abstract

This document lists errata items for FreeBSD 10.0-RELEASE, + “�” symbol.

Last modified on 2014-09-16 by gjb.

Abstract

This document lists errata items for FreeBSD 10.0-RELEASE, containing significant information discovered after the release or too late in the release cycle to be otherwise included in the release documentation. This information @@ -43,7 +43,8 @@ handling

SA-14:13.pam3�June�2014

Fix incorrect error handling in PAM policy parser

SA-14:14.openssl5�June�2014

Multiple vulnerabilities

SA-14:15.iconv24�June�2014

NULL pointer dereference and out-of-bounds array access

SA-14:16.file24�June�2014

Multiple vulnerabilities

SA-14:17.kmem8�July�2014

Kernel memory disclosure in control messages - and SCTP notifications

SA-14:18.openssl9�September�2014

Multiple vulnerabilities

3.�Open Issues

FreeBSD/i386 10.0-RELEASE running as a guest + and SCTP notifications
SA-14:18.openssl9�September�2014
Multiple vulnerabilities
SA-14:19.tcp16�September�2014
Denial of Service in TCP packet + processing.

3.�Open Issues

FreeBSD/i386 10.0-RELEASE running as a guest operating system on VirtualBox can have a problem with disk I/O access. It depends on some specific hardware configuration and does not depend on a @@ -107,7 +108,7 @@ boot
4.�Late-Breaking News
No news.

This file, and other release-related documents, can be downloaded from http://www.FreeBSD.org/snapshots/.

For questions about FreeBSD, read the documentation before - contacting <questions@FreeBSD.org>.

All users of FreeBSD stable should + contacting <questions@FreeBSD.org>.

All users of FreeBSD 10.0-STABLE should subscribe to the <stable@FreeBSD.org> mailing list.

For questions about this documentation, e-mail <doc@FreeBSD.org>.

\ No newline at end of file Modified: head/en_US.ISO8859-1/htdocs/releases/9.3R/errata.html ============================================================================== --- head/en_US.ISO8859-1/htdocs/releases/9.3R/errata.html Tue Sep 16 19:21:09 2014 (r45625) +++ head/en_US.ISO8859-1/htdocs/releases/9.3R/errata.html Tue Sep 16 19:29:22 2014 (r45626) @@ -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
Copyright � 2014 The FreeBSD Documentation Project
FreeBSD is a registered trademark of the FreeBSD Foundation.
Intel, Celeron, EtherExpress, i386, @@ -14,7 +14,7 @@ as trademarks. Where those designations appear in this document, and the FreeBSD Project was aware of the trademark claim, the designations have been followed by the “™” or the - “�” symbol.
Last modified on 2014-09-09 by gjb.
Abstract
This document lists errata items for FreeBSD 9.3-RELEASE, + “�” symbol.
Last modified on 2014-09-16 by gjb.
Abstract
This document lists errata items for FreeBSD 9.3-RELEASE, containing significant information discovered after the release or too late in the release cycle to be otherwise included in the release documentation. @@ -38,7 +38,8 @@ the snapshot).
For a list of all FreeBSD CERT security advisories, see `http://www.FreeBSD.org/security/` or `ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/`.
2.�Security Advisories
Problems described in the following security advisories have been fixed in 9.3-RELEASE. For more information, consult the individual advisories available from - `http://security.FreeBSD.org/`.
Advisory Date Topic
SA-14:18.openssl 9�September�2014
Multiple vulnerabilities
3.�Late-Breaking News
No late-breaking news.
< small>This file, and other release-related documents, + `http://security.FreeBSD.org/`.
Advisory Date Topic
SA-14:18.openssl 9�September�2014
Multiple vulnerabilities
SA-14:19.tcp 16�September�2014
Denial of Service in TCP packet + processing.
3.�Late-Breaking News
No late-breaking news.
This file, and other release-related documents, can be downloaded from http://www.FreeBSD.org/releases/.
For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
All users of FreeBSD 9.3-STABLE should From owner-svn-doc-head@FreeBSD.ORG Tue Sep 16 20:12:18 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9A31F776; Tue, 16 Sep 2014 20:12:18 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::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 83B856C7; Tue, 16 Sep 2014 20:12:18 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8GKCIIS063737; Tue, 16 Sep 2014 20:12:18 GMT (envelope-from mat@FreeBSD.org) Received: (from mat@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8GKCIBo063736; Tue, 16 Sep 2014 20:12:18 GMT (envelope-from mat@FreeBSD.org) Message-Id: <201409162012.s8GKCIBo063736@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: mat set sender to mat@FreeBSD.org using -f From: Mathieu Arnold Date: Tue, 16 Sep 2014 20:12:18 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45627 - head/en_US.ISO8859-1/books/porters-handbook/makefiles 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.18-1 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, 16 Sep 2014 20:12:18 -0000 Author: mat (ports committer) Date: Tue Sep 16 20:12:18 2014 New Revision: 45627 URL: http://svnweb.freebsd.org/changeset/doc/45627 Log: igor -Ry and some other rewording and fixes. Differential Revision: https://reviews.freebsd.org/D643 Reviewed by: wblock Sponsored by: Absolight Modified: head/en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml Tue Sep 16 19:29:22 2014 (r45626) +++ head/en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml Tue Sep 16 20:12:18 2014 (r45627) @@ -11,35 +11,34 @@ Configuring the Makefile Configuring the Makefile is pretty - simple, and again we suggest that you look at existing examples + simple, and again we suggest looking at existing examples before starting. Also, there is a sample Makefile in this handbook, so take a look and please follow the ordering of - variables and sections in that template to make your port easier + variables and sections in that template to make the port easier for others to read. - Now, consider the following problems in sequence as you - design your new Makefile: + Consider these problems in sequence during the + design of the new Makefile: The Original Source Does it live in DISTDIR as a standard gzipped tarball named something like - foozolix-1.2.tar.gz? If so, you can go on - to the next step. If not, you should look at overriding any of - the DISTVERSION, DISTNAME, + foozolix-1.2.tar.gz? If so, go on + to the next step. If not, the distribution file format might + require overriding one or more of + DISTVERSION, DISTNAME, EXTRACT_CMD, EXTRACT_BEFORE_ARGS, EXTRACT_AFTER_ARGS, - EXTRACT_SUFX, or DISTFILES - variables, depending on how alien a format your port's - distribution file is. + EXTRACT_SUFX, or + DISTFILES. - In the worst case, you can simply create your own + In the worst case, create a custom do-extract target to override the - default, though this should be rarely, if ever, - necessary. + default. This is rarely, if ever, necessary. @@ -53,17 +52,17 @@ <varname>PORTNAME</varname> and <varname>PORTVERSION</varname> - You should set PORTNAME to the base - name of your port, and PORTVERSION to the + Set PORTNAME to the base + name of the port, and PORTVERSION to the version number of the port. - - Package name should be unique among all of the ports - tree, check that there is not already a port with the same + + The package name must be unique among all of the ports + tree. Make sure that there is not already a port with the same PORTNAME and if there is add one of PKGNAMEPREFIX or PKGNAMESUFFIX. - + @@ -73,24 +72,24 @@ <varname>PORTREVISION</varname> - The PORTREVISION variable is a + PORTREVISION is a monotonically increasing value which is reset to 0 with - every increase of PORTVERSION (i.e., - every time a new official vendor release is made), and - appended to the package name if non-zero. Changes to + every increase of PORTVERSION, typically + every time there is a new official vendor release. If + PORTREVISION is non-zero, the value is + appended to the package name. Changes to PORTREVISION are used by automated tools - (e.g., pkg version, see - &man.pkg-version.8;) to highlight the fact that a new - package is available. + like &man.pkg-version.8; to determine that a new package is + available. - PORTREVISION should be increased each + PORTREVISION must be increased each time a change is made to the port that changes the generated package in any way. That includes changes that only affect a package built with non-default options. Examples of when PORTREVISION - should be bumped: + must be bumped: @@ -107,9 +106,9 @@ Changes in the packing list or the install-time - behavior of the package (e.g., change to a script which - generates initial data for the package, like ssh host - keys). + behavior of the package. For example, a change to a script which + generates initial data for the package, like &man.ssh.1; host + keys. @@ -122,7 +121,7 @@ Silent changes to the port distfile which have - significant functional differences, i.e., changes to the + significant functional differences. For example, changes to the distfile requiring a correction to distinfo with no corresponding change to PORTVERSION, where a @@ -150,30 +149,39 @@ Trivial patches to the distfile such as correction of typos, which are not important enough that users of - the package should go to the trouble of + the package have to go to the trouble of upgrading. Build fixes which cause a package to become - compilable where it was previously failing (as long as + compilable where it was previously failing. As long as the changes do not introduce any functional change on any other platforms on which the port did previously - build). Since PORTREVISION reflects + build. Since PORTREVISION reflects the content of the package, if the package was not previously buildable then there is no need to increase PORTREVISION to mark a change. - A rule of thumb is to ask yourself whether a change - committed to a port is something which everyone would - benefit from having (either because of an enhancement, fix, + A rule of thumb is to decide whether a change + committed to a port is something which some people would + benefit from having. Either because of an enhancement, fix, or by virtue that the new package will actually work at - all), and weigh that against that fact that it will cause + all. Then weigh that against that fact that it will cause everyone who regularly updates their ports tree to be - compelled to update. If yes, the - PORTREVISION should be bumped. + compelled to update. If yes, + PORTREVISION must be bumped. + + + People using binary packages will + never see the update if + PORTREVISION is not bumped. Without + increasing PORTREVISION, the + package builders have no way to detect the change and + thus, will not rebuild the package. + @@ -194,38 +202,38 @@ two version number strings. For example: &prompt.user; pkg version -t 0.031 0.29 -> + > The > output indicates that version 0.031 is considered greater than version 0.29, which may not have been obvious to the porter. - In situations such as this, the - PORTEPOCH version should be increased. + In situations such as this, + PORTEPOCH must be increased. If PORTEPOCH is nonzero it is appended to the package name as described in section 0 above. PORTEPOCH must never be decreased or reset to zero, because that would cause comparison to a - package from an earlier epoch to fail (i.e., the package - would not be detected as out of date): the new version - number (e.g., 1.0,1 in the above example) - is still numerically less than the previous version - (20000801), but the ,1 suffix is treated + package from an earlier epoch to fail. For example, the package + would not be detected as out of date. The new version + number, 1.0,1 in the above + example, is still numerically less than the previous version, + 20000801, but the ,1 suffix is treated specially by automated tools and found to be greater than the implied suffix ,0 on the earlier package. Dropping or resetting PORTEPOCH - incorrectly leads to no end of grief; if you do not - understand the above discussion, please keep after it until - you do, or ask questions on the mailing lists. + incorrectly leads to no end of grief. If the discussion + above was not clear enough, please consult the + &a.ports;. It is expected that PORTEPOCH will not be used for the majority of ports, and that sensible use of PORTVERSION can often preempt it becoming necessary if a future release of the software - should change the version structure. However, care is + changes the version structure. However, care is needed by &os; porters when a vendor release is made without an official version number — such as a code snapshot release. The temptation is to label @@ -234,11 +242,14 @@ release is made. For example, if a snapshot release is made on the date - 20000917, and the previous version of the software was - version 1.2, the snapshot release should be given a - PORTVERSION of 1.2.20000917 or similar, - not 20000917, so that the succeeding release, say 1.3, is - still a numerically greater value. + 20000917, and the previous version of the software was + version 1.2, do not use + 20000917 for + PORTVERSION. The correct way is a + PORTVERSION of + 1.2.20000917, or similar, so that the + succeeding release, say 1.3, is still a + numerically greater value. @@ -250,7 +261,7 @@ collection: PORTNAME= gtkmumble -PORTVERSION= 0.10 + PORTVERSION= 0.10 PKGNAME becomes gtkmumble-0.10. @@ -260,8 +271,8 @@ PORTVERSION= 0.10 accordingly. PORTNAME= gtkmumble -PORTVERSION= 0.10 -PORTREVISION= 1 + PORTVERSION= 0.10 + PORTREVISION= 1 PKGNAME becomes gtkmumble-0.10_1 @@ -270,9 +281,9 @@ PORTREVISION= 1 0.2 (it turns out the author actually intended 0.10 to actually mean 0.1.0, not what comes after - 0.9 - oops, too late now). Since the new minor + 0.9 - oops, too late now). Since the new minor version 2 is numerically less than the - previous version 10, the + previous version 10, PORTEPOCH must be bumped to manually force the new package to be detected as newer. Since it is a new vendor release of @@ -280,8 +291,8 @@ PORTREVISION= 1 removed from the Makefile). PORTNAME= gtkmumble -PORTVERSION= 0.2 -PORTEPOCH= 1 + PORTVERSION= 0.2 + PORTEPOCH= 1 PKGNAME becomes gtkmumble-0.2,1 @@ -291,8 +302,8 @@ PORTEPOCH= 1 variables are now: PORTNAME= gtkmumble -PORTVERSION= 0.3 -PORTEPOCH= 1 + PORTVERSION= 0.3 + PORTEPOCH= 1 PKGNAME becomes gtkmumble-0.3,1 @@ -321,9 +332,10 @@ PORTEPOCH= 1 ${PKGNAMEPREFIX}${PORTNAME}${PKGNAMESUFFIX}-${PORTVERSION}. Make sure this conforms to our guidelines for a good - package name. In particular, you are - not allowed to use a hyphen - (-) in PORTVERSION. + package name. In particular, the use of a + hyphen (-) in + PORTVERSION is not + allowed. Also, if the package name has the language- or the -compiled.specifics part (see @@ -370,8 +382,7 @@ PORTEPOCH= 1 French. The language- part is - set in the PKGNAMEPREFIX - variable. + set in PKGNAMEPREFIX. @@ -379,34 +390,30 @@ PORTEPOCH= 1 name - The first letter of the name - part should be lowercase. (The rest of the name may - contain capital letters, so use your own discretion when - converting a software name that has some capital letters - in it.) There is a tradition of naming - Perl 5 modules by prepending - p5- and converting the double-colon - separator to a hyphen. For example, the - Data::Dumper module becomes - p5-Data-Dumper. - Make sure that the port's name and version are - clearly separated and placed into the + clearly separated and placed into PORTNAME and - PORTVERSION variables. The only + PORTVERSION. The only reason for PORTNAME to contain a version part is if the upstream distribution is really named that way, as in the - textproc/libxml2 or - japanese/kinput2-freewnn ports. - Otherwise, the PORTNAME should not + textproc/libxml2 or + japanese/kinput2-freewnn ports. + Otherwise, PORTNAME cannot contain any version-specific information. It is quite normal for several ports to have the same PORTNAME, as the - www/apache* ports do; in that case, + www/apache* ports do; in that case, different versions (and different index entries) are - distinguished by the PKGNAMEPREFIX + distinguished by PKGNAMEPREFIX and PKGNAMESUFFIX values. + + There is a tradition of naming + Perl 5 modules by prepending + p5- and converting the double-colon + separator to a hyphen. For example, the + Data::Dumper module becomes + p5-Data-Dumper. @@ -419,13 +426,12 @@ PORTEPOCH= 1 (usually part of the directory name in a family of ports), the -compiled.specifics part - should state the compiled-in defaults (the hyphen is - optional). Examples are paper size and font + states the compiled-in defaults. The hyphen is + optional. Examples are paper size and font units. The -compiled.specifics - part is set in the PKGNAMESUFFIX - variable. + part is set in PKGNAMESUFFIX. @@ -446,9 +452,9 @@ PORTEPOCH= 1 beta, rc, or pre, take the first letter and put it immediately after a period. If the version string - continues after those names, the numbers should follow + continues after those names, the numbers follow the single alphabet without an extra period between - them. + them (for example, 1.0b2). The idea is to make it easier to sort ports by looking at the version string. In particular, make sure @@ -461,26 +467,28 @@ PORTEPOCH= 1 yy.mm.dd format. It is important to prefix the version with 0.0. in case a release with an actual - version number is made, which would of course be + version number is made, which would be numerically less than yyyy. - + Package name must be unique among all of the ports tree, check that there is not already a port with the same PORTNAME and if there is add one of PKGNAMEPREFIX or PKGNAMESUFFIX. - + Here are some (real) examples on how to convert the name as called by the software authors to a suitable package name: - + + Package Naming Examples + @@ -504,6 +512,15 @@ PORTEPOCH= 1 + mule-1.0.1 + (empty) + mule + 1 + 1.0.1 + mule already exists + + + EmiClock-1.0.2 (empty) emiclock @@ -608,14 +625,15 @@ PORTEPOCH= 1 - +

If there is absolutely no trace of version information in the original source and it is unlikely that the original author will ever release another version, just set the version string to 1.0 (like the piewm example above). Otherwise, ask the - original author or use the date string + original author or use the date string the source file was + released on (0.0.yyyy.mm.dd) as the version. @@ -637,12 +655,12 @@ PORTEPOCH= 1 packages on the FTP site or the CDROM. Please take a look at the current list of categories and pick the ones that are suitable for - your port. + the port. This list also determines where in the ports tree the port - is imported. If you put more than one category here, it is - assumed that the port files will be put in the subdirectory - with the name in the first category. See + is imported. If there is more than one category here, + the port files must be put in the subdirectory + with the name of the first category. See below for more discussion about how to pick the right categories. @@ -658,8 +676,8 @@ PORTEPOCH= 1 purposes. - For non-virtual categories, you will find a one-line - description in the COMMENT in that + For non-virtual categories, there is a one-line + description in COMMENT in that subdirectory's Makefile. @@ -740,7 +758,7 @@ PORTEPOCH= 1 comms Communication software. - Mostly software to talk to your serial + Mostly software to talk to the serial port. @@ -767,9 +785,9 @@ PORTEPOCH= 1 devel Development utilities. Do not put libraries here just because they are - libraries—unless they truly do not belong - anywhere else, they should not be in this - category. + libraries. They should not be + in this category unless they truly do not belong + anywhere else. @@ -788,8 +806,10 @@ PORTEPOCH= 1 editors General editors. Specialized editors go in the section for those - tools (e.g., a mathematical-formula editor will go - in math). + tools. For example, a mathematical-formula editor will + go in math, and have + editors as a second + category. @@ -802,7 +822,7 @@ PORTEPOCH= 1 emulators Emulators for other operating systems. Terminal emulators do not - belong here—X-based ones should go to + belong here. X-based ones go to x11 and text-based ones to either comms or misc, depending on the exact @@ -824,8 +844,8 @@ PORTEPOCH= 1 ftp - FTP client and server utilities. - If your port speaks both FTP and HTTP, put it + FTP client and server utilities. + If the port speaks both FTP and HTTP, put it in ftp with a secondary category of www. @@ -984,10 +1004,10 @@ PORTEPOCH= 1 misc Miscellaneous utilities - Basically things that do not belong anywhere + Things that do not belong anywhere else. If at all possible, try to find a better - category for your port than misc, - as ports tend to get overlooked in here. + category for the port than misc, + as ports tend to be overlooked in here. @@ -1212,7 +1232,7 @@ PORTEPOCH= 1 The X Window System and friends. This category is only for software that directly supports the window system. Do not put regular X - applications here; most of them should go into other + applications here. Most of them go into other x11-* categories (see below). @@ -1288,9 +1308,9 @@ PORTEPOCH= 1 Choosing the Right Category - As many of the categories overlap, you often have to - choose which of the categories should be the primary category - of your port. There are several rules that govern this issue. + As many of the categories overlap, choosing which of the + categories will be the primary category of the port can be + tedious. There are several rules that govern this issue. Here is the list of priorities, in decreasing order of precedence: @@ -1305,16 +1325,16 @@ PORTEPOCH= 1 Language specific categories always come first. For - example, if your port installs Japanese X11 fonts, then - your CATEGORIES line would read + example, if the port installs Japanese X11 fonts, then + the CATEGORIES line would read japanese x11-fonts. Specific categories are listed before less-specific - ones. For instance, an HTML editor should be listed as + ones. For instance, an HTML editor is listed as www editors, not the other way - around. Also, you should not list + around. Also, do not list net when the port belongs to any of irc, mail, news, security, @@ -1325,49 +1345,50 @@ PORTEPOCH= 1 x11 is used as a secondary category only when the primary category is a natural - language. In particular, you should not put + language. In particular, do not put x11 in the category line for X applications. - Emacs modes should be + Emacs modes are placed in the same ports category as the application supported by the mode, not in editors. For example, an Emacs mode to edit source files - of some programming language should go into + of some programming language goes into lang. - Ports which install loadable kernel modules should + Ports installing loadable kernel modules also have the virtual category kld in their CATEGORIES line. This is one of the things handled automatically by adding - kmod to the USES - line. + USES=kmod. - misc should not appear with any - other non-virtual category. If you have - misc with something else in your - CATEGORIES line, that means you can - safely delete misc and just put the - port in that other subdirectory! + misc does not appear with any + other non-virtual category. If there is + misc with something else in + CATEGORIES, that means + misc can safely be deleted and the port + placed only in the other subdirectory. - If your port truly does not belong anywhere else, + If the port truly does not belong anywhere else, put it in misc. - If you are not sure about the category, please put a - comment to that effect in your &man.send-pr.1; submission so - we can discuss it before we import it. If you are a - committer, send a note to the &a.ports; so we can discuss it + If the category is not clearly defined, please put a + comment to that effect in the port + submission in the bug database so + we can discuss it before we import it. As a committer, + send a note to the &a.ports; so we can discuss it first. Too often, new ports are imported to the wrong category only to be moved right away. This causes unnecessary and undesirable bloat in the master source repository. @@ -1381,9 +1402,9 @@ PORTEPOCH= 1 virtual categories—those that do not have a corresponding subdirectory in the ports tree— or physical categories—those that - do. The following text discusses the issues involved in - creating a new physical category so that you can understand - them before you propose one. + do. This section discusses the issues involved in creating a + new physical category. Read it thouroughly before proposing a + new one. Our existing practice has been to avoid creating a new physical category unless either a large number of ports would @@ -1407,15 +1428,15 @@ PORTEPOCH= 1 - Propose the new category on &a.ports;. You should - include a detailed rationale for the new category, - including why you feel the existing categories are not + Propose the new category on &a.ports;. Include + a detailed rationale for the new category, + including why the existing categories are not sufficient, and the list of existing ports proposed to move. (If there are new ports pending in - GNATS that would fit this + Bugzilla that would fit this category, list them too.) If you are the maintainer and/or submitter, respectively, mention that as it may - help you to make your case. + help the case. @@ -1423,10 +1444,10 @@ PORTEPOCH= 1 - If it seems that there is support for your idea, file + If it seems that there is support for the idea, file a PR which includes both the rationale and the list of existing ports that need to be moved. Ideally, this PR - should also include patches for the following: + would also include these patches: @@ -1450,7 +1471,7 @@ PORTEPOCH= 1 - (for extra credit, you can include the other files + (for extra credit, include the other files that have to change, as per the procedure in the Committer's Guide.) @@ -1459,9 +1480,9 @@ PORTEPOCH= 1 Since it affects the ports infrastructure and involves - not only performing repo-copies but also possibly running - regression tests on the build cluster, the PR should be - assigned to the &a.portmgr;. + moving and patching many ports but also possibly running + regression tests on the build cluster, assign the PR to + the &a.portmgr;. @@ -1472,10 +1493,10 @@ PORTEPOCH= 1 - Proposing a new virtual category should be similar to the + Proposing a new virtual category is similar to the above but much less involved, since no ports will actually have to move. In this case, the only patches to include in - the PR would be those to add the new category to the + the PR would be those to add the new category to CATEGORIES of the affected ports. @@ -1489,8 +1510,8 @@ PORTEPOCH= 1 effort involved to retrofit the entire existing ports collection with any kind of reorganization is daunting to say the very least. Please read the history of these proposals in - the mailing list archives before you post this idea; - furthermore, you should be prepared to be challenged to offer + the mailing list archives before posting this idea. + Furthermore, be prepared to be challenged to offer a working prototype. @@ -1499,8 +1520,8 @@ PORTEPOCH= 1 The Distribution Files The second part of the Makefile - describes the files that must be downloaded in order to build - the port, and where they can be downloaded from. + describes the files that must be downloaded to build + the port, and where they can be downloaded. <varname>DISTVERSION/DISTNAME</varname> @@ -1528,9 +1549,9 @@ PORTEPOCH= 1 Only one of PORTVERSION and - DISTVERSION can be set at a time. If you - set DISTVERSION and the derived - PORTVERSION is not right, do not use + DISTVERSION can be set at a time. If + DISTVERSION does not derive a correct + PORTVERSION, do not use DISTVERSION, set PORTVERSION to the right value and set DISTNAME with PORTNAME @@ -1539,11 +1560,11 @@ PORTEPOCH= 1 version. - The following table lists some examples of - DISTVERSION and the derived - PORTVERSION: - + + Examples of <varname>DISTVERSION</varname> and the + Derived <varname>PORTVERSION</varname> + @@ -1574,19 +1595,19 @@ PORTEPOCH= 1 - +

PKGNAMEPREFIX and PKGNAMESUFFIX do not affect DISTNAME. Also note that if WRKSRC is equal to - work/${DISTNAME} while + ${WRKDIR}/${DISTNAME} while the original source archive is named something other than ${PORTNAME}-${PORTVERSION}${EXTRACT_SUFX}, - you should probably leave DISTNAME - alone— you are better off defining - DISTFILES than having to set both + leave DISTNAME + alone— defining only + DISTFILES is easier than both DISTNAME and WRKSRC (and possibly EXTRACT_SUFX). @@ -1604,7 +1625,7 @@ PORTEPOCH= 1 FETCH if they cannot find it already on the system. - It is recommended that you put multiple sites on this + It is recommended that multiple sites are included on this list, preferably from different continents. This will safeguard against wide-area network problems. We are even planning to add support for automatically determining the @@ -1612,20 +1633,20 @@ PORTEPOCH= 1 sites will go a long way towards helping this effort. If the original tarball is part of one of the popular - archives such as SourceForge, GNU, or Perl CPAN, you may be - able refer to those sites in an easy compact form using - predefined macros (e.g., SF, - GNU or CPAN). Simply - set MASTER_SITES to one of these values. + archives such as SourceForge, GNU, or Perl CPAN, it may be + possible refer to those sites in an easy compact form using + predefined macros (for example, SF, + GNU or CPAN). + Set MASTER_SITES to one of these values. Here is an example: MASTER_SITES= GNU/make - Or you can use the older expanded format, though there - really are no reason to do so: + The older expanded format can still be used, although there + really is no reason to do so: MASTER_SITES= ${MASTER_SITE_GNU} -MASTER_SITE_SUBDIR= make + MASTER_SITE_SUBDIR= make These values and variables are defined in /usr/ports/Mk/bsd.sites.mk. There are @@ -1635,7 +1656,7 @@ MASTER_SITE_SUBDIR= makeSeveral magic macros exist for popular sites with a predictable directory structure. For these, just use the abbreviation and the system will try to - guess the correct subdirectory for you. + guess the correct subdirectory automatically. MASTER_SITES= SF @@ -1647,7 +1668,7 @@ MASTER_SITE_SUBDIR= makeThis can also be written as MASTER_SITES= SF -MASTER_SITE_SUBDIR= stardict/WyabdcRealPeopleTTS/${PORTVERSION} + MASTER_SITE_SUBDIR= stardict/WyabdcRealPeopleTTS/${PORTVERSION} Popular Magic <varname>MASTER_SITES</varname> @@ -1828,11 +1849,11 @@ MASTER_SITE_SUBDIR= stardict/WyabdcRealP this (slightly stripped for the example):</para> <programlisting>PORTNAME= pkg -PORTVERSION= 1.2.7 + PORTVERSION= 1.2.7 -USE_GITHUB= yes -GH_ACCOUNT= freebsd -GH_COMMIT= f53e577</programlisting> + USE_GITHUB= yes + GH_ACCOUNT= freebsd + GH_COMMIT= f53e577</programlisting> <para>It will automatically have <varname>MASTER_SITES</varname> set to <literal>GH @@ -1852,13 +1873,13 @@ GH_COMMIT= f53e577</programlisting> this (slightly stripped for the example):</para> <programlisting>PORTNAME= pkg-devel -PORTVERSION= 1.3.0.a.20140411 + PORTVERSION= 1.3.0.a.20140411 -USE_GITHUB= yes -GH_ACCOUNT= freebsd -GH_PROJECT= pkg -GH_TAGNAME= ${GH_COMMIT} -GH_COMMIT= 6dbb17b</programlisting> + USE_GITHUB= yes + GH_ACCOUNT= freebsd + GH_PROJECT= pkg + GH_TAGNAME= ${GH_COMMIT} + GH_COMMIT= 6dbb17b</programlisting> <para>It will automatically have <varname>MASTER_SITES</varname> set to <literal>GH @@ -1872,16 +1893,16 @@ GH_COMMIT= 6dbb17b</programlisting> <sect2 xml:id="makefile-extract_sufx"> <title><varname>EXTRACT_SUFX</varname> - If you have one distribution file, and it uses an odd + If there is one distribution file, and it uses an odd suffix to indicate the compression mechanism, set EXTRACT_SUFX. For example, if the distribution file was named foo.tar.gzip instead of the more normal - foo.tar.gz, you would write: + foo.tar.gz, write:DISTNAME= foo -EXTRACT_SUFX= .tar.gzip + EXTRACT_SUFX= .tar.gzipThe USES=tar[:xxx], @@ -1893,9 +1914,8 @@ EXTRACT_SUFX= .tar.gzip .tar.gz. - You never need to set both - EXTRACT_SUFX and - DISTFILES. + As EXTRACT_SUFX is only used in + DISTFILES, only set one of them.. @@ -1929,11 +1949,11 @@ EXTRACT_SUFX= .tar.gzipEXTRACT_ONLY.DISTFILES= source.tar.gz manual.html -EXTRACT_ONLY= source.tar.gz + EXTRACT_ONLY= source.tar.gz - If none of the - DISTFILES should be uncompressed then set - EXTRACT_ONLY to the empty string. + When none of the DISTFILES need to be + uncompressed, set EXTRACT_ONLY to the empty + string.EXTRACT_ONLY= @@ -1941,14 +1961,14 @@ EXTRACT_ONLY= source.tar.gz<varname>PATCHFILES</varname> - If your port requires some additional patches that are - available by FTP or HTTP, set PATCHFILES to + If the port requires some additional patches that are + available by FTP or HTTP, set PATCHFILES to the names of the files and PATCH_SITES to the URL of the directory that contains them (the format is the same as MASTER_SITES). If the patch is not relative to the top of the source tree - (i.e., WRKSRC) because it contains some + (that is, WRKSRC) because it contains some extra pathnames, set PATCH_DIST_STRIP accordingly. For instance, if all the pathnames in the patch have an extra foozolix-1.0/ in front of the @@ -1961,16 +1981,16 @@ EXTRACT_ONLY= source.tar.gz.bz2 or .xz. * DIFF OUTPUT TRUNCATED AT 1000 LINES * From owner-svn-doc-head@FreeBSD.ORG Tue Sep 16 22:17:03 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9D8C7432; Tue, 16 Sep 2014 22:17:03 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::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 892B63DD; Tue, 16 Sep 2014 22:17:03 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8GMH3Gt021477; Tue, 16 Sep 2014 22:17:03 GMT (envelope-from gavin@FreeBSD.org) Received: (from gavin@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8GMH3oR021476; Tue, 16 Sep 2014 22:17:03 GMT (envelope-from gavin@FreeBSD.org) Message-Id: <201409162217.s8GMH3oR021476@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: gavin set sender to gavin@FreeBSD.org using -f From: Gavin Atkinson Date: Tue, 16 Sep 2014 22:17:03 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45628 - head/en_US.ISO8859-1/books/handbook/security 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.18-1 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, 16 Sep 2014 22:17:03 -0000 Author: gavin Date: Tue Sep 16 22:17:03 2014 New Revision: 45628 URL: http://svnweb.freebsd.org/changeset/doc/45628 Log: Clarify that only 10.0-RELEASE and above can automatically generate certificates for Sendmail at the moment. Modified: head/en_US.ISO8859-1/books/handbook/security/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/security/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/security/chapter.xml Tue Sep 16 20:12:18 2014 (r45627) +++ head/en_US.ISO8859-1/books/handbook/security/chapter.xml Tue Sep 16 22:17:03 2014 (r45628) @@ -1968,7 +1968,9 @@ Email Address []: - To configure Sendmail, add the + In &os; 10.0-RELEASE and above, it is possible to create + a self-signed certificate for Sendmail + automatically. To enable this, add the following lines to /etc/rc.conf: From owner-svn-doc-head@FreeBSD.ORG Wed Sep 17 08:38:33 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B900378C; Wed, 17 Sep 2014 08:38:33 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::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 A386ECC4; Wed, 17 Sep 2014 08:38:33 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8H8cXoY011190; Wed, 17 Sep 2014 08:38:33 GMT (envelope-from mat@FreeBSD.org) Received: (from mat@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8H8cXCA011188; Wed, 17 Sep 2014 08:38:33 GMT (envelope-from mat@FreeBSD.org) Message-Id: <201409170838.s8H8cXCA011188@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: mat set sender to mat@FreeBSD.org using -f From: Mathieu Arnold Date: Wed, 17 Sep 2014 08:38:33 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45629 - in head/en_US.ISO8859-1: books/porters-handbook/special htdocs/gnome/docs 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.18-1 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, 17 Sep 2014 08:38:33 -0000 Author: mat (ports committer) Date: Wed Sep 17 08:38:32 2014 New Revision: 45629 URL: http://svnweb.freebsd.org/changeset/doc/45629 Log: Update the USE_AUTOTOOLS/USE_GNOME as of r368357 of the ports tree. Sponsored by: Absolight Modified: head/en_US.ISO8859-1/books/porters-handbook/special/chapter.xml head/en_US.ISO8859-1/htdocs/gnome/docs/porting.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/special/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/special/chapter.xml Tue Sep 16 22:17:03 2014 (r45628) +++ head/en_US.ISO8859-1/books/porters-handbook/special/chapter.xml Wed Sep 17 08:38:32 2014 (r45629) @@ -783,9 +783,8 @@ CMAKE_SOURCE_PATH= ${WRKSRC}/subp At the time of writing, tool can be one of autoconf, autoheader, automake, - aclocal, libtool - (deprecated), libtoolize, - libltdl. It can also be one the older + aclocal, libtoolize. + It can also be one the older legacy of autoconf213, autoheader213, automake14, @@ -803,12 +802,11 @@ CMAKE_SOURCE_PATH= ${WRKSRC}/subp - <command>libtool</command> + <command>libtool</command> and <command>libtoolize</command> - The use of USE_AUTOTOOLS=libtool is - deprecated. Now all ports that ship with their own copy of - libtool (search for a file named ltmain.sh) need to have - USES=libtool. Also, if a port has + Ports shipping with their own copy of libtool (search for + a file named ltmain.sh) need to have + USES=libtool. If a port has USE_AUTOTOOLS=libtoolize it probably also needs USES=libtool. See the USES=libtool section in - <command>libltdl</command> + <filename>libltdl.so</filename> - Some ports make use of the libltdl + Some ports make use of the libltdl.so library package, which is part of the libtool suite. Use of this library does not automatically necessitate the use of - libtool itself, so a separate construct - is provided. + libtool itself. If the port needs + libltdl.so, add a dependency on + it: - USE_AUTOTOOLS= libltdl - - Currently, all this does is to bring in a - LIB_DEPENDS on the appropriate - libltdl port, and is provided as a - convenience function to help eliminate any dependencies on - the autotools ports outside of the - USE_AUTOTOOLS framework. There are no - optional operations for this tool. + LIB_DEPENDS= libltdl.so:${PORTSDIR}/devel/libltdl Modified: head/en_US.ISO8859-1/htdocs/gnome/docs/porting.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/gnome/docs/porting.xml Tue Sep 16 22:17:03 2014 (r45628) +++ head/en_US.ISO8859-1/htdocs/gnome/docs/porting.xml Wed Sep 17 08:38:32 2014 (r45629) @@ -332,13 +332,7 @@ GCONF_SCHEMAS= CDDB-Slave2.schemas gnome They also use the GNU configure system. If your port installs shared libraries, and includes an `ltmain.sh` script in its `${WRKSRC}` directory, you should add - `USE_AUTOTOOLS="libtool":15` to your port's Makefile. - However, if your port uses custom `LIBTOOLFLAGS`, you - must use `USE_AUTOTOOLS="libtool":13:inc` instead. If you have - to use `libtool:X:inc`, you must also add - `lthack` to `USE_GNOME`. In general, though, - `lthack` is deprecated, and should only be used if - absolutely necessary.
+ `USES=libtool` to your port's Makefile.
From owner-svn-doc-head@FreeBSD.ORG Wed Sep 17 09:14:57 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D387F59B; Wed, 17 Sep 2014 09:14:57 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::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 BE3AE17B; Wed, 17 Sep 2014 09:14:57 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8H9EveF029480; Wed, 17 Sep 2014 09:14:57 GMT (envelope-from dumbbell@FreeBSD.org) Received: (from dumbbell@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8H9EvPQ029479; Wed, 17 Sep 2014 09:14:57 GMT (envelope-from dumbbell@FreeBSD.org) Message-Id: <201409170914.s8H9EvPQ029479@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: dumbbell set sender to dumbbell@FreeBSD.org using -f From: Jean-Sebastien Pedron Date: Wed, 17 Sep 2014 09:14:57 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45630 - head/en_US.ISO8859-1/books/porters-handbook/versions 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.18-1 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, 17 Sep 2014 09:14:57 -0000 Author: dumbbell (src committer) Date: Wed Sep 17 09:14:57 2014 New Revision: 45630 URL: http://svnweb.freebsd.org/changeset/doc/45630 Log: Document __FreeBSD_version value 1100035 Tested by: mat@ Modified: head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Wed Sep 17 08:38:32 2014 (r45629) +++ head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Wed Sep 17 09:14:57 2014 (r45630) @@ -5400,6 +5400,13 @@ (rev 271666). + + 1100035 + September 17, 2014 + 11.0-CURRENT after i915 HW context support + (rev 271705). + +

From owner-svn-doc-head@FreeBSD.ORG Wed Sep 17 18:57:46 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8A966C92; Wed, 17 Sep 2014 18:57:46 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::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 6AB9A95E; Wed, 17 Sep 2014 18:57:46 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8HIvkCi011728; Wed, 17 Sep 2014 18:57:46 GMT (envelope-from bcr@FreeBSD.org) Received: (from bcr@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8HIvkRH011727; Wed, 17 Sep 2014 18:57:46 GMT (envelope-from bcr@FreeBSD.org) Message-Id: <201409171857.s8HIvkRH011727@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: bcr set sender to bcr@FreeBSD.org using -f From: Benedict Reuschling Date: Wed, 17 Sep 2014 18:57:46 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45631 - 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.18-1 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, 17 Sep 2014 18:57:46 -0000 Author: bcr Date: Wed Sep 17 18:57:45 2014 New Revision: 45631 URL: http://svnweb.freebsd.org/changeset/doc/45631 Log: Put in the missing revision r40792: Prefer the use of service(1) to explicit invocation of /etc/rc.d scripts: service(1) puts things in one place and abstracts them. Also, it's less typing and easier to autocomplete. Submitted by: Bjoern Heidotting Obtained from: The FreeBSD German Documentation Project 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 Sep 17 09:14:57 2014 (r45630) +++ head/de_DE.ISO8859-1/books/handbook/advanced-networking/chapter.xml Wed Sep 17 18:57:45 2014 (r45631) @@ -1376,7 +1376,7 @@ ifconfig_wlan0="DHCP" Nun k�nnen Sie Ihr drahtloses Ger�t starten: - &prompt.root; /etc/rc.d/netif start + &prompt.root; service netif start Nachdem Sie das Ger�t aktiviert haben, k�nnen Sie mit ifconfig den @@ -1512,7 +1512,7 @@ ifconfig_wlan0="WPA DHCP"Nun k�nnen Sie Ihr Netzger�t aktivieren: - &prompt.root; /etc/rc.d/netif start + &prompt.root; service netif start Starting wpa_supplicant. DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6 @@ -1715,10 +1715,9 @@ wlan0: flags=8843<UP,BROADCAST,RUNNIN ifconfig_wlan0="WPA DHCP" Nun k�nnen Sie Ihr drahtloses Ger�t - �ber das rc.d-System aktivieren: - &prompt.root; /etc/rc.d/netif start + &prompt.root; service netif start Starting wpa_supplicant. DHCPREQUEST on wlan0 to 255.255.255.255 port 67 interval 7 DHCPREQUEST on wlan0 to 255.255.255.255 port 67 interval 15 @@ -1815,7 +1814,7 @@ ifconfig_wlan0="WPA DHCP"Nun k�nnen Sie Ihr drahtloses Ger�t aktivieren: - &prompt.root; /etc/rc.d/netif start + &prompt.root; service netif start Starting wpa_supplicant. DHCPREQUEST on wlan0 to 255.255.255.255 port 67 interval 7 DHCPREQUEST on wlan0 to 255.255.255.255 port 67 interval 15 @@ -1930,7 +1929,7 @@ wlan0: flags=8843<UP,BROADCAST,RUNNIN Zuletzt m�ssen Sie die Netzwerkkarte noch aktivieren: - &prompt.root; /etc/rc.d/netif start + &prompt.root; service netif start Starting wpa_supplicant. DHCPREQUEST on wlan0 to 255.255.255.255 port 67 interval 7 DHCPREQUEST on wlan0 to 255.255.255.255 port 67 interval 15 @@ -2328,7 +2327,7 @@ wpa_pairwise=CCMP TKIP Vorwort @@ -216,9 +216,9 @@ (Das X Window System) wurde neu geschrieben. Der Schwerpunkt liegt auf modernen - Benutzeroberfl�chen unter &xfree86; 4.X wie + Benutzeroberfl�chen wie KDE und - GNOME. + GNOME unter &xorg;. From owner-svn-doc-head@FreeBSD.ORG Wed Sep 17 23:13:48 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5536C51A; Wed, 17 Sep 2014 23:13:48 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::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 40D1E80F; Wed, 17 Sep 2014 23:13:48 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8HNDmCN036603; Wed, 17 Sep 2014 23:13:48 GMT (envelope-from gavin@FreeBSD.org) Received: (from gavin@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8HNDmMO036602; Wed, 17 Sep 2014 23:13:48 GMT (envelope-from gavin@FreeBSD.org) Message-Id: <201409172313.s8HNDmMO036602@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: gavin set sender to gavin@FreeBSD.org using -f From: Gavin Atkinson Date: Wed, 17 Sep 2014 23:13:48 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45633 - head/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.18-1 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, 17 Sep 2014 23:13:48 -0000 Author: gavin Date: Wed Sep 17 23:13:47 2014 New Revision: 45633 URL: http://svnweb.freebsd.org/changeset/doc/45633 Log: Switch to the recommended URL for the old Google Chart API Note that this code uses the old API which is officially deprecated, however converting this to use the new Chart API will take some time. Obtained from: https://developers.google.com/chart/image/docs/making_charts Modified: head/share/xml/templates.usergroups.xsl Modified: head/share/xml/templates.usergroups.xsl ============================================================================== --- head/share/xml/templates.usergroups.xsl Wed Sep 17 19:03:36 2014 (r45632) +++ head/share/xml/templates.usergroups.xsl Wed Sep 17 23:13:47 2014 (r45633) @@ -16,7 +16,7 @@ - + &title; From owner-svn-doc-head@FreeBSD.ORG Wed Sep 17 23:33:54 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BB097B40; Wed, 17 Sep 2014 23:33:54 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::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 A6BAD9B4; Wed, 17 Sep 2014 23:33:54 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8HNXscs046354; Wed, 17 Sep 2014 23:33:54 GMT (envelope-from kib@FreeBSD.org) Received: (from kib@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8HNXsuM046352; Wed, 17 Sep 2014 23:33:54 GMT (envelope-from kib@FreeBSD.org) Message-Id: <201409172333.s8HNXsuM046352@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: kib set sender to kib@FreeBSD.org using -f From: Konstantin Belousov Date: Wed, 17 Sep 2014 23:33:54 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45634 - head/en_US.ISO8859-1/books/porters-handbook/versions 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.18-1 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, 17 Sep 2014 23:33:54 -0000 Author: kib (src committer) Date: Wed Sep 17 23:33:54 2014 New Revision: 45634 URL: http://svnweb.freebsd.org/changeset/doc/45634 Log: Document __FreeBSD_version 1100036. Sponsored by: The FreeBSD Foundation Modified: head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Wed Sep 17 23:13:47 2014 (r45633) +++ head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Wed Sep 17 23:33:54 2014 (r45634) @@ -5407,6 +5407,14 @@ (rev 271705). + + 1100036 + September 17, 2014 + Version bump to have ABI note distinguish binaries + ready for strict &man.mmap.2; flags checking + (rev 271724). + + From owner-svn-doc-head@FreeBSD.ORG Thu Sep 18 12:03:41 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7B8A12AD; Thu, 18 Sep 2014 12:03:41 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::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 66A9794E; Thu, 18 Sep 2014 12:03:41 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8IC3fXF095861; Thu, 18 Sep 2014 12:03:41 GMT (envelope-from mat@FreeBSD.org) Received: (from mat@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8IC3f9v095860; Thu, 18 Sep 2014 12:03:41 GMT (envelope-from mat@FreeBSD.org) Message-Id: <201409181203.s8IC3f9v095860@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: mat set sender to mat@FreeBSD.org using -f From: Mathieu Arnold Date: Thu, 18 Sep 2014 12:03:41 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45635 - head/en_US.ISO8859-1/books/porters-handbook/uses 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.18-1 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, 18 Sep 2014 12:03:41 -0000 Author: mat (ports committer) Date: Thu Sep 18 12:03:40 2014 New Revision: 45635 URL: http://svnweb.freebsd.org/changeset/doc/45635 Log: Add USES=autoreconf Differential Revision: https://reviews.freebsd.org/D792 Reviewed by: wblock, tijl Sponsored by: Absolight Modified: head/en_US.ISO8859-1/books/porters-handbook/uses/chapter.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/uses/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/uses/chapter.xml Wed Sep 17 23:33:54 2014 (r45634) +++ head/en_US.ISO8859-1/books/porters-handbook/uses/chapter.xml Thu Sep 18 12:03:40 2014 (r45635) @@ -56,6 +56,28 @@ gcc 4.7 based one. + + autoreconf + + (none), build + + Runs autoreconf. It encapsulates + the aclocal, + autoconf, + autoheader, + automake, autopoint, + and libtoolize commands. Each command + applies to + ${CONFIGURE_WRKSRC}/configure.ac. If + configure.ac defines subdirectories + with their own configure.ac using + AC_CONFIG_SUBDIRS, + autoreconf will recursively update + those as well. The :build argument + only adds build time dependencies on those tools but does + not run autoreconf. + + bison From owner-svn-doc-head@FreeBSD.ORG Thu Sep 18 20:37:54 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 43547EF1; Thu, 18 Sep 2014 20:37:54 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::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 2D116FFF; Thu, 18 Sep 2014 20:37:54 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8IKbsQT049491; Thu, 18 Sep 2014 20:37:54 GMT (envelope-from dumbbell@FreeBSD.org) Received: (from dumbbell@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8IKbshp049490; Thu, 18 Sep 2014 20:37:54 GMT (envelope-from dumbbell@FreeBSD.org) Message-Id: <201409182037.s8IKbshp049490@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: dumbbell set sender to dumbbell@FreeBSD.org using -f From: Jean-Sebastien Pedron Date: Thu, 18 Sep 2014 20:37:54 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45636 - head/en_US.ISO8859-1/books/porters-handbook/versions 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.18-1 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, 18 Sep 2014 20:37:54 -0000 Author: dumbbell (src committer) Date: Thu Sep 18 20:37:53 2014 New Revision: 45636 URL: http://svnweb.freebsd.org/changeset/doc/45636 Log: Document __FreeBSD_version value 1000717 Modified: head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Thu Sep 18 12:03:40 2014 (r45635) +++ head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Thu Sep 18 20:37:53 2014 (r45636) @@ -5140,6 +5140,13 @@ + 1000717 + September 18, 2014 + 10-STABLE after i915 HW context support + (rev 271816). + + + 1100000 October 10, 2013 11.0-CURRENT From owner-svn-doc-head@FreeBSD.ORG Thu Sep 18 20:51:13 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 67B59F40; Thu, 18 Sep 2014 20:51:13 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::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 5258D289; Thu, 18 Sep 2014 20:51:13 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8IKpD7B058052; Thu, 18 Sep 2014 20:51:13 GMT (envelope-from gjb@FreeBSD.org) Received: (from gjb@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8IKpD0k058050; Thu, 18 Sep 2014 20:51:13 GMT (envelope-from gjb@FreeBSD.org) Message-Id: <201409182051.s8IKpD0k058050@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: gjb set sender to gjb@FreeBSD.org using -f From: Glen Barber Date: Thu, 18 Sep 2014 20:51:13 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45637 - head/en_US.ISO8859-1/books/handbook/bibliography 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.18-1 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, 18 Sep 2014 20:51:13 -0000 Author: gjb Date: Thu Sep 18 20:51:12 2014 New Revision: 45637 URL: http://svnweb.freebsd.org/changeset/doc/45637 Log: Mention Design and Implementation of the FreeBSD Operating System, 2nd Ed in the bibliography. Sponsored by: The FreeBSD Foundation Modified: head/en_US.ISO8859-1/books/handbook/bibliography/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/bibliography/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/bibliography/chapter.xml Thu Sep 18 20:37:53 2014 (r45636) +++ head/en_US.ISO8859-1/books/handbook/bibliography/chapter.xml Thu Sep 18 20:51:12 2014 (r45637) @@ -379,6 +379,14 @@ + Marshall Kirk McKusick, George V. Neville-Neil, + Robert N. M. Watson The Design and Implementation + of the FreeBSD Operating System, 2nd Ed.. + Westford, Mass. : Pearson Education, Inc., 2014. + ISBN 0-321-96897-2 + + + Stevens, W. Richard. TCP/IP Illustrated, Volume 1: The Protocols. Reading, Mass. : Addison-Wesley, 1996. ISBN 0-201-63346-9 From owner-svn-doc-head@FreeBSD.ORG Thu Sep 18 23:09:08 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2A0DB23E; Thu, 18 Sep 2014 23:09:08 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::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 15A41269; Thu, 18 Sep 2014 23:09:08 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8IN973D022529; Thu, 18 Sep 2014 23:09:07 GMT (envelope-from gavin@FreeBSD.org) Received: (from gavin@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8IN97lT022528; Thu, 18 Sep 2014 23:09:07 GMT (envelope-from gavin@FreeBSD.org) Message-Id: <201409182309.s8IN97lT022528@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: gavin set sender to gavin@FreeBSD.org using -f From: Gavin Atkinson Date: Thu, 18 Sep 2014 23:09:07 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45638 - 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.18-1 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, 18 Sep 2014 23:09:08 -0000 Author: gavin Date: Thu Sep 18 23:09:07 2014 New Revision: 45638 URL: http://svnweb.freebsd.org/changeset/doc/45638 Log: Hopefully fix the display of the most recent videos, by using protocol- relative URLs. Unfortunately, I am unable to test this fix locally at the moment. Modified: head/en_US.ISO8859-1/htdocs/community.xsl Modified: head/en_US.ISO8859-1/htdocs/community.xsl ============================================================================== --- head/en_US.ISO8859-1/htdocs/community.xsl Thu Sep 18 20:51:12 2014 (r45637) +++ head/en_US.ISO8859-1/htdocs/community.xsl Thu Sep 18 23:09:07 2014 (r45638) @@ -78,19 +78,19 @@ Loading...
- -

Advisory	Date	Topic
SA-14:18.openssl	9�September�2014	Multiple vulnerabilities
SA-14:19.tcp	16�September�2014	Denial of Service in TCP packet + processing.

&os;/&arch.pc98; Hardware Notes

FreeBSD 10.0-RELEASE Errata

The FreeBSD Project

FreeBSD 10.0-RELEASE Errata

The FreeBSD Project

3.�Open Issues

3.�Open Issues

4.�Late-Breaking News

FreeBSD 9.3-RELEASE Errata

FreeBSD 9.3-RELEASE Errata

The FreeBSD Project

2.�Security Advisories

3.�Late-Breaking News

3.�Late-Breaking News