From owner-svn-doc-head@freebsd.org Sun Sep 23 10:29:40 2018 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 10B8B10B2429; Sun, 23 Sep 2018 10:29:40 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A90E370719; Sun, 23 Sep 2018 10:29:39 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 9E0591481; Sun, 23 Sep 2018 10:29:39 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w8NATdFR060727; Sun, 23 Sep 2018 10:29:39 GMT (envelope-from bcr@FreeBSD.org) Received: (from bcr@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w8NATdNu060726; Sun, 23 Sep 2018 10:29:39 GMT (envelope-from bcr@FreeBSD.org) Message-Id: <201809231029.w8NATdNu060726@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bcr set sender to bcr@FreeBSD.org using -f From: Benedict Reuschling Date: Sun, 23 Sep 2018 10:29:39 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52291 - head/en_US.ISO8859-1/books/arch-handbook/newbus X-SVN-Group: doc-head X-SVN-Commit-Author: bcr X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/arch-handbook/newbus X-SVN-Commit-Revision: 52291 X-SVN-Commit-Repository: doc 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.27 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2018 10:29:40 -0000 Author: bcr Date: Sun Sep 23 10:29:39 2018 New Revision: 52291 URL: https://svnweb.freebsd.org/changeset/doc/52291 Log: Clean up the newbus chapter for the following errors found by textproc/igor: - wrap long line - leave an empty line after tag - use two spaces at sentence start Modified: head/en_US.ISO8859-1/books/arch-handbook/newbus/chapter.xml Modified: head/en_US.ISO8859-1/books/arch-handbook/newbus/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/arch-handbook/newbus/chapter.xml Sat Sep 22 16:15:39 2018 (r52290) +++ head/en_US.ISO8859-1/books/arch-handbook/newbus/chapter.xml Sun Sep 23 10:29:39 2018 (r52291) @@ -22,18 +22,38 @@ Provided under the FreeBSD Documentation License. --> -<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="newbus"> - <info><title>Newbus + + + Newbus + - JeroenRuigrok van der Werven (asmodai) -
asmodai@FreeBSD.org
- Written by - HitenPandya -
hiten@uk.FreeBSD.org
- + + + Jeroen + Ruigrok van der Werven (asmodai) + + +
+ asmodai@FreeBSD.org +
+ + Written by + + + + Hiten + Pandya + + +
+ hiten@uk.FreeBSD.org +
+ + - Special thanks to Matthew N. Dodd, Warner Losh, Bill Paul, Doug Rabson, Mike Smith, Peter Wemm and Scott @@ -79,11 +99,11 @@ Block devices performed in a way that used fixed size blocks [of data]. This type of driver depended on the so-called buffer cache, - which had cached accessed blocks of data in a - dedicated part of memory. Often this buffer cache was - based on write-behind, which meant that when data was modified - in memory it got synced to disk whenever the system did its - periodical disk flushing, thus optimizing writes. + which had cached accessed blocks of data in a dedicated part + of memory. Often this buffer cache was based on write-behind, + which meant that when data was modified in memory it got + synced to disk whenever the system did its periodical disk + flushing, thus optimizing writes. @@ -143,7 +163,7 @@ entity in the system. For instance each PCI device is represented by a Newbus device. Any device in the system can have children; a device which has children is often called a - bus. Examples of common + bus. Examples of common busses in the system are ISA and PCI, which manage lists of devices attached to ISA and PCI busses respectively. @@ -193,9 +213,10 @@ port-mapped registers (some hardware supports both). This support is integrated into the resource allocation - mechanism. When a resource is allocated, a driver can retrieve - the associated bus_space_tag_t and - bus_space_handle_t from the + mechanism. When a resource is allocated, a driver can retrieve + the associated bus_space_tag_t and bus_space_handle_t from the resource. Newbus also allows for definitions of interface methods in @@ -219,12 +240,12 @@ table declared by the driver. A device can later detach from its driver and re-attach to a new driver with a new method - table. This allows dynamic replacement of drivers which can be + table. This allows dynamic replacement of drivers which can be useful for driver development. The interfaces are described by an interface definition language similar to the language used to define vnode operations - for file systems. The interface would be stored in a methods + for file systems. The interface would be stored in a methods file (which would normally be named foo_if.m). @@ -279,7 +300,7 @@ contains methods suitable for devices which have children, including methods to access bus specific per-device information &man.bus.generic.read.ivar.9; and - &man.bus.generic.write.ivar.9;, event + &man.bus.generic.write.ivar.9;, event notification (child_detached, driver_added) and From owner-svn-doc-head@freebsd.org Sun Sep 23 11:38:05 2018 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 47BC210B361C; Sun, 23 Sep 2018 11:38:05 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F1B7273082; Sun, 23 Sep 2018 11:38:04 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id EC653201D; Sun, 23 Sep 2018 11:38:04 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w8NBc4Zu098382; Sun, 23 Sep 2018 11:38:04 GMT (envelope-from bcr@FreeBSD.org) Received: (from bcr@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w8NBc4AP098381; Sun, 23 Sep 2018 11:38:04 GMT (envelope-from bcr@FreeBSD.org) Message-Id: <201809231138.w8NBc4AP098381@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bcr set sender to bcr@FreeBSD.org using -f From: Benedict Reuschling Date: Sun, 23 Sep 2018 11:38:04 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52292 - head/en_US.ISO8859-1/books/arch-handbook/usb X-SVN-Group: doc-head X-SVN-Commit-Author: bcr X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/arch-handbook/usb X-SVN-Commit-Revision: 52292 X-SVN-Commit-Repository: doc 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.27 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2018 11:38:05 -0000 Author: bcr Date: Sun Sep 23 11:38:04 2018 New Revision: 52292 URL: https://svnweb.freebsd.org/changeset/doc/52292 Log: Fix over 400 errors reported by textproc/igor for this file: - wrap long lines - use two spaces at sentence start - bad tag indent - space after content - use tabs instead of spaces Modified: head/en_US.ISO8859-1/books/arch-handbook/usb/chapter.xml Modified: head/en_US.ISO8859-1/books/arch-handbook/usb/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/arch-handbook/usb/chapter.xml Sun Sep 23 10:29:39 2018 (r52291) +++ head/en_US.ISO8859-1/books/arch-handbook/usb/chapter.xml Sun Sep 23 11:38:04 2018 (r52292) @@ -4,26 +4,41 @@ $FreeBSD$ --> - - USB Devices + + + USB Devices + - NickHibmaWritten by + + + Nick + Hibma + + Written by + - MurrayStokelyModifications for Handbook made by + + + Murray + Stokely + + Modifications for Handbook made by + - - Introduction - Universal Serial Bus (USB) + Universal Serial Bus + (USB) NetBSD The Universal Serial Bus (USB) is a new way of attaching - devices to personal computers. The bus architecture features + devices to personal computers. The bus architecture features two-way communication and has been developed as a response to devices becoming smarter and requiring more interaction with the host. USB support is included in all current PC chipsets and is @@ -39,210 +54,228 @@ a shared code base. For the implementation of the USB subsystem a number of features of USB are important. - Lennart Augustsson has done most of the implementation of - the USB support for the NetBSD project. Many thanks for this - incredible amount of work. Many thanks also to Ardy and Dirk for - their comments and proofreading of this paper. + Lennart Augustsson has done most of the + implementation of the USB support for the NetBSD project. + Many thanks for this incredible amount of work. Many thanks + also to Ardy and Dirk for their comments and proofreading of + this paper. - Devices connect to ports on the computer - directly or on devices called hubs, forming a treelike device - structure. + + Devices connect to ports on the computer directly or on + devices called hubs, forming a treelike device + structure. + - The devices can be connected and disconnected at - run time. + + The devices can be connected and disconnected at run + time. + - Devices can suspend themselves and trigger - resumes of the host system + + Devices can suspend themselves and trigger resumes of + the host system + - As the devices can be powered from the bus, the - host software has to keep track of power budgets for each - hub. + + As the devices can be powered from the bus, the host + software has to keep track of power budgets for each + hub. + - Different quality of service requirements by the - different device types together with the maximum of 126 - devices that can be connected to the same bus, require proper - scheduling of transfers on the shared bus to take full - advantage of the 12Mbps bandwidth available. (over 400Mbps - with USB 2.0) + + Different quality of service requirements by the + different device types together with the maximum of 126 + devices that can be connected to the same bus, require + proper scheduling of transfers on the shared bus to take + full advantage of the 12Mbps bandwidth available. (over + 400Mbps with USB 2.0) + - Devices are intelligent and contain easily - accessible information about themselves + + Devices are intelligent and contain easily accessible + information about themselves + The development of drivers for the USB subsystem and devices connected to it is supported by the specifications that have - been developed and will be developed. These specifications are + been developed and will be developed. These specifications are publicly available from the USB home pages. Apple has been very strong in pushing for standards based drivers, by making drivers for the generic classes available in their operating system MacOS and discouraging the use of separate drivers for each new - device. This chapter tries to collate essential information for a - basic understanding of the USB 2.0 implementation - stack in FreeBSD/NetBSD. It is recommended however to read it - together with the relevant 2.0 specifications and other - developer resources: - + device. This chapter tries to collate essential information for + a basic understanding of the USB 2.0 implementation stack in + FreeBSD/NetBSD. It is recommended however to read it together + with the relevant 2.0 specifications and other developer + resources: + USB 2.0 Specification (http://www.usb.org/developers/docs/usb20_docs/) + xlink:href="http://www.usb.org/developers/docs/usb20_docs/">http://www.usb.org/developers/docs/usb20_docs/) - + Universal Host Controller Interface (UHCI) Specification (ftp://ftp.netbsd.org/pub/NetBSD/misc/blymn/uhci11d.pdf) + xlink:href="ftp://ftp.netbsd.org/pub/NetBSD/misc/blymn/uhci11d.pdf">ftp://ftp.netbsd.org/pub/NetBSD/misc/blymn/uhci11d.pdf) Open Host Controller Interface (OHCI) Specification(ftp://ftp.compaq.com/pub/supportinformation/papers/hcir1_0a.pdf) - - + xlink:href="ftp://ftp.compaq.com/pub/supportinformation/papers/hcir1_0a.pdf">ftp://ftp.compaq.com/pub/supportinformation/papers/hcir1_0a.pdf) + + - Developer section of USB home page (http://www.usb.org/developers/) + Developer section of USB home page + (http://www.usb.org/developers/) Structure of the USB Stack - The USB support in FreeBSD can be split into three - layers. The lowest layer contains the host controller driver, - providing a generic interface to the hardware and its scheduling - facilities. It supports initialisation of the hardware, - scheduling of transfers and handling of completed and/or failed - transfers. Each host controller driver implements a virtual hub - providing hardware independent access to the registers - controlling the root ports on the back of the machine. + The USB support in FreeBSD can be split into three layers. + The lowest layer contains the host controller driver, + providing a generic interface to the hardware and its + scheduling facilities. It supports initialisation of the + hardware, scheduling of transfers and handling of completed + and/or failed transfers. Each host controller driver + implements a virtual hub providing hardware independent access + to the registers controlling the root ports on the back of the + machine. The middle layer handles the device connection and - disconnection, basic initialisation of the device, driver - selection, the communication channels (pipes) and does - resource management. This services layer also controls the - default pipes and the device requests transferred over - them. + disconnection, basic initialisation of the device, driver + selection, the communication channels (pipes) and does + resource management. This services layer also controls the + default pipes and the device requests transferred over + them. The top layer contains the individual drivers supporting - specific (classes of) devices. These drivers implement the - protocol that is used over the pipes other than the default - pipe. They also implement additional functionality to make the - device available to other parts of the kernel or userland. They - use the USB driver interface (USBDI) exposed by the services - layer. + specific (classes of) devices. These drivers implement the + protocol that is used over the pipes other than the default + pipe. They also implement additional functionality to make + the device available to other parts of the kernel or userland. + They use the USB driver interface (USBDI) exposed by the + services layer. Host Controllers - USBhost controllers + USBhost + controllers The host controller (HC) controls the transmission of - packets on the bus. Frames of 1 millisecond are used. At the + packets on the bus. Frames of 1 millisecond are used. At the start of each frame the host controller generates a Start of Frame (SOF) packet. The SOF packet is used to synchronise to the start of the - frame and to keep track of the frame number. Within each frame + frame and to keep track of the frame number. Within each frame packets are transferred, either from host to device (out) or - from device to host (in). Transfers are always initiated by the - host (polled transfers). Therefore there can only be one host - per USB bus. Each transfer of a packet has a status stage in + from device to host (in). Transfers are always initiated by the + host (polled transfers). Therefore there can only be one host + per USB bus. Each transfer of a packet has a status stage in which the recipient of the data can return either ACK (acknowledge reception), NAK (retry), STALL (error condition) or nothing (garbled data stage, device not available or - disconnected). Section 8.5 of the USB 2.0 Specification - explains the details of packets in more - detail. Four different types of transfers can occur on a USB - bus: control, bulk, interrupt and isochronous. The types of - transfers and their characteristics are described below. + disconnected). Section 8.5 of the USB 2.0 Specification + explains the details of packets in more detail. Four different + types of transfers can occur on a USB bus: control, bulk, + interrupt and isochronous. The types of transfers and their + characteristics are described below. Large transfers between the device on the USB bus and the device driver are split up into multiple packets by the host controller or the HC driver. Device requests (control transfers) to the default endpoints - are special. They consist of two or three phases: SETUP, DATA - (optional) and STATUS. The set-up packet is sent to the - device. If there is a data phase, the direction of the data - packet(s) is given in the set-up packet. The direction in the - status phase is the opposite of the direction during the data - phase, or IN if there was no data phase. The host controller - hardware also provides registers with the current status of the - root ports and the changes that have occurred since the last - reset of the status change register. Access to these registers - is provided through a virtualised hub as suggested in the USB - specification. The virtual hub must comply with the hub - device class given in chapter 11 of that specification. It must - provide a default pipe through which device requests can be sent - to it. It returns the standard andhub class specific set of - descriptors. It should also provide an interrupt pipe that - reports changes happening at its ports. There are currently two - specifications for host controllers available: Universal Host - Controller Interface (UHCI) from Intel - and Open Host Controller Interface (OHCI) - from Compaq, Microsoft, and National - Semiconductor. The UHCI specification has been - designed to reduce hardware complexity by requiring the host - controller driver to supply a complete schedule of the transfers - for each frame. OHCI type controllers are much more independent - by providing a more abstract interface doing a lot of work - themselves. + are special. They consist of two or three phases: SETUP, DATA + (optional) and STATUS. The set-up packet is sent to the device. + If there is a data phase, the direction of the data packet(s) is + given in the set-up packet. The direction in the status phase + is the opposite of the direction during the data phase, or IN if + there was no data phase. The host controller hardware also + provides registers with the current status of the root ports and + the changes that have occurred since the last reset of the + status change register. Access to these registers is provided + through a virtualised hub as suggested in the USB specification. + The virtual hub must comply with the hub device class given in + chapter 11 of that specification. It must provide a default + pipe through which device requests can be sent to it. It + returns the standard andhub class specific set of descriptors. + It should also provide an interrupt pipe that reports changes + happening at its ports. There are currently two specifications + for host controllers available: Universal Host Controller + Interface (UHCI) from Intel and Open Host + Controller Interface (OHCI) from Compaq, + Microsoft, and National Semiconductor. The + UHCI specification has been designed to + reduce hardware complexity by requiring the host controller + driver to supply a complete schedule of the transfers for each + frame. OHCI type controllers are much more independent by + providing a more abstract interface doing a lot of work + themselves. UHCI - USBUHCI + + USB + UHCI + The UHCI host controller maintains a framelist with 1024 - pointers to per frame data structures. It understands two - different data types: transfer descriptors (TD) and queue - heads (QH). Each TD represents a packet to be communicated to - or from a device endpoint. QHs are a means to groupTDs (and - QHs) together. + pointers to per frame data structures. It understands two + different data types: transfer descriptors (TD) and queue + heads (QH). Each TD represents a packet to be communicated to + or from a device endpoint. QHs are a means to groupTDs (and + QHs) together. - Each transfer consists of one or more packets. The UHCI - driver splits large transfers into multiple packets. For every - transfer, apart from isochronous transfers, a QH is - allocated. For every type of transfer these QHs are collected - at a QH for that type. Isochronous transfers have to be - executed first because of the fixed latency requirement and - are directly referred to by the pointer in the framelist. The - last isochronous TD refers to the QH for interrupt transfers - for that frame. All QHs for interrupt transfers point at the - QH for control transfers, which in turn points at the QH for - bulk transfers. The following diagram gives a graphical - overview of this: + Each transfer consists of one or more packets. The UHCI + driver splits large transfers into multiple packets. For + every transfer, apart from isochronous transfers, a QH is + allocated. For every type of transfer these QHs are collected + at a QH for that type. Isochronous transfers have to be + executed first because of the fixed latency requirement and + are directly referred to by the pointer in the framelist. The + last isochronous TD refers to the QH for interrupt transfers + for that frame. All QHs for interrupt transfers point at the + QH for control transfers, which in turn points at the QH for + bulk transfers. The following diagram gives a graphical + overview of this: This results in the following schedule being run in each - frame. After fetching the pointer for the current frame from - the framelist the controller first executes the TDs for all - the isochronous packets in that frame. The last of these TDs - refers to the QH for the interrupt transfers for - thatframe. The host controller will then descend from that QH - to the QHs for the individual interrupt transfers. After - finishing that queue, the QH for the interrupt transfers will - refer the controller to the QH for all control transfers. It - will execute all the subqueues scheduled there, followed by - all the transfers queued at the bulk QH. To facilitate the - handling of finished or failed transfers different types of - interrupts are generated by the hardware at the end of each - frame. In the last TD for a transfer the Interrupt-On - Completion bit is set by the HC driver to flag an interrupt - when the transfer has completed. An error interrupt is flagged - if a TD reaches its maximum error count. If the short packet - detect bit is set in a TD and less than the set packet length - is transferred this interrupt is flagged to notify - the controller driver of the completed transfer. It is the host - controller driver's task to find out which transfer has - completed or produced an error. When called the interrupt - service routine will locate all the finished transfers and - call their callbacks. + frame. After fetching the pointer for the current frame from + the framelist the controller first executes the TDs for all + the isochronous packets in that frame. The last of these TDs + refers to the QH for the interrupt transfers for thatframe. + The host controller will then descend from that QH to the QHs + for the individual interrupt transfers. After finishing that + queue, the QH for the interrupt transfers will refer the + controller to the QH for all control transfers. It will + execute all the subqueues scheduled there, followed by all the + transfers queued at the bulk QH. To facilitate the handling + of finished or failed transfers different types of interrupts + are generated by the hardware at the end of each frame. In + the last TD for a transfer the Interrupt-On Completion bit is + set by the HC driver to flag an interrupt when the transfer + has completed. An error interrupt is flagged if a TD reaches + its maximum error count. If the short packet detect bit is + set in a TD and less than the set packet length is transferred + this interrupt is flagged to notify the controller driver of + the completed transfer. It is the host controller driver's + task to find out which transfer has completed or produced an + error. When called the interrupt service routine will locate + all the finished transfers and call their callbacks. Refer to the UHCI Specification for a more elaborate description. @@ -252,56 +285,60 @@ OHCI - USBOHCI - Programming an OHCI host controller is much simpler. The - controller assumes that a set of endpoints is available, and - is aware of scheduling priorities and the ordering of the - types of transfers in a frame. The main data structure used by - the host controller is the endpoint descriptor (ED) to which - a queue of transfer descriptors (TDs) is attached. The ED - contains the maximum packet size allowed for an endpoint and - the controller hardware does the splitting into packets. The - pointers to the data buffers are updated after each transfer - and when the start and end pointer are equal, the TD is - retired to the done-queue. The four types of endpoints - (interrupt, isochronous, control, and bulk) have their - own queues. Control and bulk endpoints are queued each at - their own queue. Interrupt EDs are queued in a tree, with the - level in the tree defining the frequency at which they - run. + + USB + OHCI + + Programming an OHCI host controller is much simpler. The + controller assumes that a set of endpoints is available, and + is aware of scheduling priorities and the ordering of the + types of transfers in a frame. The main data structure used + by the host controller is the endpoint descriptor (ED) to + which a queue of transfer descriptors (TDs) is attached. The + ED contains the maximum packet size allowed for an endpoint + and the controller hardware does the splitting into packets. + The pointers to the data buffers are updated after each + transfer and when the start and end pointer are equal, the TD + is retired to the done-queue. The four types of endpoints + (interrupt, isochronous, control, and bulk) have their own + queues. Control and bulk endpoints are queued each at their + own queue. Interrupt EDs are queued in a tree, with the level + in the tree defining the frequency at which they run. + The schedule being run by the host controller in each - frame looks as follows. The controller will first run the - non-periodic control and bulk queues, up to a time limit set - by the HC driver. Then the interrupt transfers for that frame - number are run, by using the lower five bits of the frame - number as an index into level 0 of the tree of interrupts - EDs. At the end of this tree the isochronous EDs are connected - and these are traversed subsequently. The isochronous TDs - contain the frame number of the first frame the transfer - should be run in. After all the periodic transfers have been - run, the control and bulk queues are traversed - again. Periodically the interrupt service routine is called to - process the done queue and call the callbacks for each - transfer and reschedule interrupt and isochronous - endpoints. + frame looks as follows. The controller will first run the + non-periodic control and bulk queues, up to a time limit set + by the HC driver. Then the interrupt transfers for that frame + number are run, by using the lower five bits of the frame + number as an index into level 0 of the tree of interrupts EDs. + At the end of this tree the isochronous EDs are connected and + these are traversed subsequently. The isochronous TDs contain + the frame number of the first frame the transfer should be run + in. After all the periodic transfers have been run, the + control and bulk queues are traversed again. Periodically the + interrupt service routine is called to process the done queue + and call the callbacks for each transfer and reschedule + interrupt and isochronous endpoints. See the UHCI Specification for a more - elaborate description. The middle layer - provides access to the device in a controlled way and - maintains resources in use by the different drivers and the - services layer. The layer takes care of the following - aspects: + elaborate description. The middle layer provides access to + the device in a controlled way and maintains resources in use + by the different drivers and the services layer. The layer + takes care of the following aspects: - The device configuration - information - The pipes to communicate with a - device - Probing and attaching and detaching form a - device. + + The device configuration information + + + The pipes to communicate with a device + + + Probing and attaching and detaching form a + device. + - @@ -312,238 +349,259 @@ Device Configuration Information Each device provides different levels of configuration - information. Each device has one or more configurations, of - which one is selected during probe/attach. A configuration - provides power and bandwidth requirements. Within each - configuration there can be multiple interfaces. A device - interface is a collection of endpoints. For example USB - speakers can have an interface for the audio data (Audio - Class) and an interface for the knobs, dials and buttons (HID - Class). All interfaces in a configuration are active at the - same time and can be attached to by different drivers. Each - interface can have alternates, providing different quality of - service parameters. In for example cameras this is used to - provide different frame sizes and numbers of frames per - second. + information. Each device has one or more configurations, of + which one is selected during probe/attach. A configuration + provides power and bandwidth requirements. Within each + configuration there can be multiple interfaces. A device + interface is a collection of endpoints. For example USB + speakers can have an interface for the audio data (Audio + Class) and an interface for the knobs, dials and buttons (HID + Class). All interfaces in a configuration are active at the + same time and can be attached to by different drivers. Each + interface can have alternates, providing different quality of + service parameters. In for example cameras this is used to + provide different frame sizes and numbers of frames per + second. Within each interface, 0 or more endpoints can be - specified. Endpoints are the unidirectional access points for - communicating with a device. They provide buffers to - temporarily store incoming or outgoing data from the - device. Each endpoint has a unique address within - a configuration, the endpoint's number plus its direction. The - default endpoint, endpoint 0, is not part of any interface and - available in all configurations. It is managed by the services - layer and not directly available to device drivers. + specified. Endpoints are the unidirectional access points for + communicating with a device. They provide buffers to + temporarily store incoming or outgoing data from the device. + Each endpoint has a unique address within a configuration, the + endpoint's number plus its direction. The default endpoint, + endpoint 0, is not part of any interface and available in all + configurations. It is managed by the services layer and not + directly available to device drivers. + --> This hierarchical configuration information is described - in the device by a standard set of descriptors (see section 9.6 - of the USB specification). They can be requested through - the Get Descriptor Request. The services layer caches these - descriptors to avoid unnecessary transfers on the USB - bus. Access to the descriptors is provided through function - calls. + in the device by a standard set of descriptors (see section + 9.6 of the USB specification). They can be requested through + the Get Descriptor Request. The services layer caches these + descriptors to avoid unnecessary transfers on the USB bus. + Access to the descriptors is provided through function + calls. - Device descriptors: General information about - the device, like Vendor, Product and Revision Id, supported - device class, subclass and protocol if applicable, maximum - packet size for the default endpoint, etc. + + Device descriptors: General information about the + device, like Vendor, Product and Revision Id, supported + device class, subclass and protocol if applicable, maximum + packet size for the default endpoint, etc. + - Configuration descriptors: The number of - interfaces in this configuration, suspend and resume - functionality supported and power - requirements. + + Configuration descriptors: The number of interfaces in + this configuration, suspend and resume functionality + supported and power requirements. + - Interface descriptors: interface class, - subclass and protocol if applicable, number of alternate - settings for the interface and the number of - endpoints. + + Interface descriptors: interface class, subclass and + protocol if applicable, number of alternate settings for + the interface and the number of endpoints. + - Endpoint descriptors: Endpoint address, - direction and type, maximum packet size supported and - polling frequency if type is interrupt endpoint. There is no - descriptor for the default endpoint (endpoint 0) and it is - never counted in an interface descriptor. + + Endpoint descriptors: Endpoint address, direction and + type, maximum packet size supported and polling frequency + if type is interrupt endpoint. There is no descriptor for + the default endpoint (endpoint 0) and it is never counted + in an interface descriptor. + - String descriptors: In the other descriptors - string indices are supplied for some fields.These can be - used to retrieve descriptive strings, possibly in multiple - languages. - + + String descriptors: In the other descriptors string + indices are supplied for some fields.These can be used to + retrieve descriptive strings, possibly in multiple + languages. + Class specifications can add their own descriptor types - that are available through the GetDescriptor Request. + that are available through the GetDescriptor Request. Pipes Communication to end points on a device flows - through so-called pipes. Drivers submit transfers to endpoints - to a pipe and provide a callback to be called on completion or - failure of the transfer (asynchronous transfers) or wait for - completion (synchronous transfer). Transfers to an endpoint - are serialised in the pipe. A transfer can either complete, - fail or time-out (if a time-out has been set). There are two - types of time-outs for transfers. Time-outs can happen due to - time-out on the USBbus (milliseconds). These time-outs are - seen as failures and can be due to disconnection of the - device. A second form of time-out is implemented in software - and is triggered when a transfer does not complete within a - specified amount of time (seconds). These are caused by a - device acknowledging negatively (NAK) the transferred - packets. The cause for this is the device not being ready to - receive data, buffer under- or overrun or protocol - errors. + through so-called pipes. Drivers submit transfers to + endpoints to a pipe and provide a callback to be called on + completion or failure of the transfer (asynchronous transfers) + or wait for completion (synchronous transfer). Transfers to + an endpoint are serialised in the pipe. A transfer can either + complete, fail or time-out (if a time-out has been set). + There are two types of time-outs for transfers. Time-outs can + happen due to time-out on the USBbus (milliseconds). These + time-outs are seen as failures and can be due to disconnection + of the device. A second form of time-out is implemented in + software and is triggered when a transfer does not complete + within a specified amount of time (seconds). These are caused + by a device acknowledging negatively (NAK) the transferred + packets. The cause for this is the device not being ready to + receive data, buffer under- or overrun or protocol + errors. If a transfer over a pipe is larger than the maximum - packet size specified in the associated endpoint descriptor, - the host controller (OHCI) or the HC driver (UHCI) will split - the transfer into packets of maximum packet size, with the - last packet possibly smaller than the maximum - packet size. + packet size specified in the associated endpoint descriptor, + the host controller (OHCI) or the HC driver (UHCI) will split + the transfer into packets of maximum packet size, with the + last packet possibly smaller than the maximum packet + size. Sometimes it is not a problem for a device to return less - data than requested. For example abulk-in-transfer to a modem - might request 200 bytes of data, but the modem has only 5 - bytes available at that time. The driver can set the short - packet (SPD) flag. It allows the host controller to accept a - packet even if the amount of data transferred is less than - requested. This flag is only valid for in-transfers, as the - amount of data to be sent to a device is always known - beforehand. If an unrecoverable error occurs in a device - during a transfer the pipe is stalled. Before any more data is - accepted or sent the driver needs to resolve the cause of the - stall and clear the endpoint stall condition through send the - clear endpoint halt device request over the default - pipe. The default endpoint should never stall. + data than requested. For example abulk-in-transfer to a modem + might request 200 bytes of data, but the modem has only 5 + bytes available at that time. The driver can set the short + packet (SPD) flag. It allows the host controller to accept a + packet even if the amount of data transferred is less than + requested. This flag is only valid for in-transfers, as the + amount of data to be sent to a device is always known + beforehand. If an unrecoverable error occurs in a device + during a transfer the pipe is stalled. Before any more data + is accepted or sent the driver needs to resolve the cause of + the stall and clear the endpoint stall condition through send + the clear endpoint halt device request over the default pipe. + The default endpoint should never stall. There are four different types of endpoints and - corresponding pipes: - Control pipe / default pipe: There is - one control pipe per device, connected to the default endpoint - (endpoint 0). The pipe carries the device requests and - associated data. The difference between transfers over the - default pipe and other pipes is that the protocol for - the transfers is described in the USB specification. These - requests are used to reset and configure the device. A basic - set of commands that must be supported by each device is - provided in chapter 9 of the USB specification. The - commands supported on this pipe can be extended by a device - class specification to support additional - functionality. + corresponding pipes: - Control pipe / default pipe: There is + one control pipe per device, connected to the default endpoint + (endpoint 0). The pipe carries the device requests and + associated data. The difference between transfers over the + default pipe and other pipes is that the protocol for the + transfers is described in the USB specification. These + requests are used to reset and configure the device. A basic + set of commands that must be supported by each device is + provided in chapter 9 of the USB specification. The commands + supported on this pipe can be extended by a device class + specification to support additional functionality. - Bulk pipe: This is the USB equivalent to a raw - transmission medium. - Interrupt pipe: The host sends a request for - data to the device and if the device has nothing to send, it - will NAK the data packet. Interrupt transfers are scheduled - at a frequency specified when creating the - pipe. + + Bulk pipe: This is the USB equivalent to a raw + transmission medium. + - Isochronous pipe: These pipes are intended for + + Interrupt pipe: The host sends a request for data to + the device and if the device has nothing to send, it will + NAK the data packet. Interrupt transfers are scheduled at + a frequency specified when creating the + pipe. + + + + Isochronous pipe: These pipes are intended for isochronous data, for example video or audio streams, with - fixed latency, but no guaranteed delivery. Some support for - pipes of this type is available in the current - implementation. Packets in control, bulk and interrupt - transfers are retried if an error occurs during transmission - or the device acknowledges the packet negatively (NAK) due to - for example lack of buffer space to store the incoming - data. Isochronous packets are however not retried in case of - failed delivery or NAK of a packet as this might violate the - timing constraints. + fixed latency, but no guaranteed delivery. Some support + for pipes of this type is available in the current + implementation. Packets in control, bulk and interrupt + transfers are retried if an error occurs during + transmission or the device acknowledges the packet + negatively (NAK) due to for example lack of buffer space + to store the incoming data. Isochronous packets are + however not retried in case of failed delivery or NAK of a + packet as this might violate the timing + constraints. + The availability of the necessary bandwidth is calculated - during the creation of the pipe. Transfers are scheduled within - frames of 1 millisecond. The bandwidth allocation within a - frame is prescribed by the USB specification, section 5.6 [ - 2]. Isochronous and interrupt transfers are allowed to consume - up to 90% of the bandwidth within a frame. Packets for control - and bulk transfers are scheduled after all isochronous and - interrupt packets and will consume all the remaining - bandwidth. + during the creation of the pipe. Transfers are scheduled + within frames of 1 millisecond. The bandwidth allocation + within a frame is prescribed by the USB specification, section + 5.6 [ 2]. Isochronous and interrupt transfers are allowed to + consume up to 90% of the bandwidth within a frame. Packets + for control and bulk transfers are scheduled after all + isochronous and interrupt packets and will consume all the + remaining bandwidth. More information on scheduling of transfers and bandwidth - reclamation can be found in chapter 5 of the USB specification, - section 1.3 of the UHCI specification, and section - 3.4.2 of the OHCI specification. - + reclamation can be found in chapter 5 of the USB + specification, section 1.3 of the UHCI specification, and + section 3.4.2 of the OHCI specification. Device Probe and Attach - USBprobe + + USB + probe + + After the notification by the hub that a new device has been connected, the service layer switches on the port, providing the - device with 100 mA of current. At this point the device is in - its default state and listening to device address 0. The + device with 100 mA of current. At this point the device is in + its default state and listening to device address 0. The services layer will proceed to retrieve the various descriptors - through the default pipe. After that it will send a Set Address + through the default pipe. After that it will send a Set Address request to move the device away from the default device address - (address 0). Multiple device drivers might be able to support - the device. For example a modem driver might be able to support - an ISDN TA through the AT compatibility interface. A driver for + (address 0). Multiple device drivers might be able to support + the device. For example a modem driver might be able to support + an ISDN TA through the AT compatibility interface. A driver for that specific model of the ISDN adapter might however be able to - provide much better support for this device. To support this + provide much better support for this device. To support this flexibility, the probes return priorities indicating their level - of support. Support for a specific revision of a product ranks - the highest and the generic driver the lowest priority. It might - also be that multiple drivers could attach to one device if - there are multiple interfaces within one configuration. Each + of support. Support for a specific revision of a product ranks + the highest and the generic driver the lowest priority. It + might also be that multiple drivers could attach to one device + if there are multiple interfaces within one configuration. Each driver only needs to support a subset of the interfaces. The probing for a driver for a newly attached device checks - first for device specific drivers. If not found, the probe code + first for device specific drivers. If not found, the probe code iterates over all supported configurations until a driver - attaches in a configuration. To support devices with multiple + attaches in a configuration. To support devices with multiple drivers on different interfaces, the probe iterates over all interfaces in a configuration that have not yet been claimed by - a driver. Configurations that exceed the power budget for the - hub are ignored. During attach the driver should initialise the + a driver. Configurations that exceed the power budget for the + hub are ignored. During attach the driver should initialise the device to its proper state, but not reset it, as this will make the device disconnect itself from the bus and restart the - probing process for it. To avoid consuming unnecessary bandwidth - should not claim the interrupt pipe at attach time, but - should postpone allocating the pipe until the file is opened and - the data is actually used. When the file is closed the pipe + probing process for it. To avoid consuming unnecessary + bandwidth should not claim the interrupt pipe at attach time, + but should postpone allocating the pipe until the file is opened + and the data is actually used. When the file is closed the pipe should be closed again, even though the device might still be attached. Device Disconnect and Detach - USBdisconnect + + USB + disconnect + + A device driver should expect to receive errors during any - transaction with the device. The design of USB supports and - encourages the disconnection of devices at any point in - time. Drivers should make sure that they do the right thing - when the device disappears. + transaction with the device. The design of USB supports and + encourages the disconnection of devices at any point in time. + Drivers should make sure that they do the right thing when the + device disappears. Furthermore a device that has been disconnected and - reconnected will not be reattached at the same device - instance. This might change in the future when more devices - support serial numbers (see the device descriptor) or other - means of defining an identity for a device have been - developed. + reconnected will not be reattached at the same device + instance. This might change in the future when more devices + support serial numbers (see the device descriptor) or other + means of defining an identity for a device have been + developed. The disconnection of a device is signaled by a hub in the - interrupt packet delivered to the hub driver. The status - change information indicates which port has seen a connection - change. The device detach method for all device drivers for - the device connected on that port are called and the structures - cleaned up. If the port status indicates that in the mean time - a device has been connected to that port, the procedure for - probing and attaching the device will be started. A device - reset will produce a disconnect-connect sequence on the hub - and will be handled as described above. - + interrupt packet delivered to the hub driver. The status + change information indicates which port has seen a connection + change. The device detach method for all device drivers for + the device connected on that port are called and the + structures cleaned up. If the port status indicates that in + the mean time a device has been connected to that port, the + procedure for probing and attaching the device will be + started. A device reset will produce a disconnect-connect + sequence on the hub and will be handled as described + above. @@ -552,31 +610,31 @@ This part is unclear, is it an unformatted code exampl The protocol used over pipes other than the default pipe is undefined by the USB specification. Information on this can be - found from various sources. The most accurate source is the - developer's section on the USB home pages. - From these pages, a growing number of deviceclass specifications are - available. These specifications specify what a compliant device - should look like from a driver perspective, basic functionality - it needs to provide and the protocol that is to be used over the + found from various sources. The most accurate source is the + developer's section on the USB home pages. From these pages, a + growing number of deviceclass specifications are available. + These specifications specify what a compliant device should look + like from a driver perspective, basic functionality it needs to + provide and the protocol that is to be used over the communication channels. The USB specification includes the - description of the Hub Class. A class specification for Human + description of the Hub Class. A class specification for Human Interface Devices (HID) has been created to cater for keyboards, - tablets, bar-code readers, buttons, knobs, switches, etc. A + tablets, bar-code readers, buttons, knobs, switches, etc. A third example is the class specification for mass storage - devices. For a full list of device classes see the developers + devices. For a full list of device classes see the developers section on the USB home pages. For many devices the protocol information has not yet been - published however. Information on the protocol being used might - be available from the company making the device. Some companies + published however. Information on the protocol being used might + be available from the company making the device. Some companies will require you to sign a Non -Disclosure Agreement (NDA) - before giving you the specifications. This in most cases + before giving you the specifications. This in most cases precludes making the driver open source. Another good source of information is the Linux driver - sources, as a number of companies have started to provide drivers - for Linux for their devices. It is always a good idea to contact - the authors of those drivers for their source of + sources, as a number of companies have started to provide + drivers for Linux for their devices. It is always a good idea + to contact the authors of those drivers for their source of information. Example: Human Interface Devices The specification for the @@ -586,54 +644,58 @@ This part is unclear, is it an unformatted code exampl For example audio speakers provide endpoints to the digital to analogue converters and possibly an extra pipe for a - microphone. They also provide a HID endpoint in a separate - interface for the buttons and dials on the front of the - device. The same is true for the monitor control class. It is + microphone. They also provide a HID endpoint in a separate *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-head@freebsd.org Sun Sep 23 15:12:18 2018 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 64A3710909D2; Sun, 23 Sep 2018 15:12:18 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1A6AF79334; Sun, 23 Sep 2018 15:12:18 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 156334801; Sun, 23 Sep 2018 15:12:18 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w8NFCHZO010772; Sun, 23 Sep 2018 15:12:17 GMT (envelope-from ryusuke@FreeBSD.org) Received: (from ryusuke@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w8NFCH8N010771; Sun, 23 Sep 2018 15:12:17 GMT (envelope-from ryusuke@FreeBSD.org) Message-Id: <201809231512.w8NFCH8N010771@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: ryusuke set sender to ryusuke@FreeBSD.org using -f From: Ryusuke SUZUKI Date: Sun, 23 Sep 2018 15:12:17 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52293 - head/en_US.ISO8859-1/htdocs/releases X-SVN-Group: doc-head X-SVN-Commit-Author: ryusuke X-SVN-Commit-Paths: head/en_US.ISO8859-1/htdocs/releases X-SVN-Commit-Revision: 52293 X-SVN-Commit-Repository: doc 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.27 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2018 15:12:18 -0000 Author: ryusuke Date: Sun Sep 23 15:12:17 2018 New Revision: 52293 URL: https://svnweb.freebsd.org/changeset/doc/52293 Log: Corrct a link to the FreeBSDD-Stable, because the "Using FreeBSD-Stable" section of Handbook was restored. Reviewed by: gjb Modified: head/en_US.ISO8859-1/htdocs/releases/index.xml Modified: head/en_US.ISO8859-1/htdocs/releases/index.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/releases/index.xml Sun Sep 23 11:38:04 2018 (r52292) +++ head/en_US.ISO8859-1/htdocs/releases/index.xml Sun Sep 23 15:12:17 2018 (r52293) @@ -83,7 +83,7 @@ page.

The latest snapshots from our FreeBSD-STABLE + href="&base;/doc/en_US.ISO8859-1/books/handbook/current-stable.html#stable">FreeBSD-STABLE and FreeBSD-CURRENT branches are also available. Please see Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F3AE210946A7; Sun, 23 Sep 2018 18:19:12 +0000 (UTC) (envelope-from ebrandi@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9913D7DBE0; Sun, 23 Sep 2018 18:19:12 +0000 (UTC) (envelope-from ebrandi@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 8F6FB64FC; Sun, 23 Sep 2018 18:19:12 +0000 (UTC) (envelope-from ebrandi@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w8NIJCZl003306; Sun, 23 Sep 2018 18:19:12 GMT (envelope-from ebrandi@FreeBSD.org) Received: (from ebrandi@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w8NIJCou003305; Sun, 23 Sep 2018 18:19:12 GMT (envelope-from ebrandi@FreeBSD.org) Message-Id: <201809231819.w8NIJCou003305@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: ebrandi set sender to ebrandi@FreeBSD.org using -f From: Edson Brandi Date: Sun, 23 Sep 2018 18:19:12 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52294 - head/en_US.ISO8859-1/articles/freebsd-releng X-SVN-Group: doc-head X-SVN-Commit-Author: ebrandi X-SVN-Commit-Paths: head/en_US.ISO8859-1/articles/freebsd-releng X-SVN-Commit-Revision: 52294 X-SVN-Commit-Repository: doc 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.27 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2018 18:19:13 -0000 Author: ebrandi Date: Sun Sep 23 18:19:12 2018 New Revision: 52294 URL: https://svnweb.freebsd.org/changeset/doc/52294 Log: Fixing Typo into freebsd-releng article (respectfully -> respectively) The word "respectfully" was used and in the context of the paragraph the correct word should be "respectively". Reviewed by: bcr Approved by: bcr Differential Revision: https://reviews.freebsd.org/D17292 Modified: head/en_US.ISO8859-1/articles/freebsd-releng/releng-building.xml Modified: head/en_US.ISO8859-1/articles/freebsd-releng/releng-building.xml ============================================================================== --- head/en_US.ISO8859-1/articles/freebsd-releng/releng-building.xml Sun Sep 23 15:12:17 2018 (r52293) +++ head/en_US.ISO8859-1/articles/freebsd-releng/releng-building.xml Sun Sep 23 18:19:12 2018 (r52294) @@ -158,7 +158,7 @@ KERNEL="GENERIC64" class="directory">/releng/scripts-snapshot/scripts or /releng/scripts-release/scripts - respectfully, to avoid collisions between an + respectively, to avoid collisions between an RC build from a releng branch versus a STABLE snapshot from the respective stable branch. From owner-svn-doc-head@freebsd.org Sun Sep 23 18:41:55 2018 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 191441094FBE; Sun, 23 Sep 2018 18:41:55 +0000 (UTC) (envelope-from ebrandi@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C3C887E859; Sun, 23 Sep 2018 18:41:54 +0000 (UTC) (envelope-from ebrandi@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id BE4F569A5; Sun, 23 Sep 2018 18:41:54 +0000 (UTC) (envelope-from ebrandi@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w8NIfse5017933; Sun, 23 Sep 2018 18:41:54 GMT (envelope-from ebrandi@FreeBSD.org) Received: (from ebrandi@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w8NIfsbA017929; Sun, 23 Sep 2018 18:41:54 GMT (envelope-from ebrandi@FreeBSD.org) Message-Id: <201809231841.w8NIfsbA017929@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: ebrandi set sender to ebrandi@FreeBSD.org using -f From: Edson Brandi Date: Sun, 23 Sep 2018 18:41:54 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52295 - in head/pt_BR.ISO8859-1/articles: . committers-guide X-SVN-Group: doc-head X-SVN-Commit-Author: ebrandi X-SVN-Commit-Paths: in head/pt_BR.ISO8859-1/articles: . committers-guide X-SVN-Commit-Revision: 52295 X-SVN-Commit-Repository: doc 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.27 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2018 18:41:55 -0000 Author: ebrandi Date: Sun Sep 23 18:41:53 2018 New Revision: 52295 URL: https://svnweb.freebsd.org/changeset/doc/52295 Log: pt_BR.ISO8859-1/articles/committers-guide: New pt_BR translation into .po format * content synchronized with en_US document (rev 52061) * article.xml converted to .po * .po file was translated to pt_BR * .po and .xml file has been set to UTF-8 encoding * information about volunteers who translated and/or revised the document was added to the header of the .po file Approved by: gabor (mentor, implicit) Obtained from: The FreeBSD Brazilian Portuguese Documentation Project Added: head/pt_BR.ISO8859-1/articles/committers-guide/ head/pt_BR.ISO8859-1/articles/committers-guide/Makefile (contents, props changed) head/pt_BR.ISO8859-1/articles/committers-guide/article.xml (contents, props changed) head/pt_BR.ISO8859-1/articles/committers-guide/pt_BR.po (contents, props changed) Modified: head/pt_BR.ISO8859-1/articles/Makefile Modified: head/pt_BR.ISO8859-1/articles/Makefile ============================================================================== --- head/pt_BR.ISO8859-1/articles/Makefile Sun Sep 23 18:19:12 2018 (r52294) +++ head/pt_BR.ISO8859-1/articles/Makefile Sun Sep 23 18:41:53 2018 (r52295) @@ -7,6 +7,7 @@ SUBDIR = SUBDIR+= bsdl-gpl SUBDIR+= building-products +SUBDIR+= committers-guide SUBDIR+= contributing SUBDIR+= contributors SUBDIR+= cups Added: head/pt_BR.ISO8859-1/articles/committers-guide/Makefile ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/pt_BR.ISO8859-1/articles/committers-guide/Makefile Sun Sep 23 18:41:53 2018 (r52295) @@ -0,0 +1,24 @@ +# +# The FreeBSD Documentation Project +# The FreeBSD Brazilian Portuguese Documentation Project +# +# $FreeBSD$ +# +# Article: Commiters Guide + +MAINTAINER=ebrandi@FreeBSD.org + +DOC?= article + +FORMATS?= html html-split +WITH_ARTICLE_TOC?= YES + +INSTALL_COMPRESSED?= gz +INSTALL_ONLY_COMPRESSED?= + +SRCS= article.xml + +URL_RELPREFIX?= ../../../.. +DOC_PREFIX?= ${.CURDIR}/../../.. + +.include "${DOC_PREFIX}/share/mk/doc.project.mk" Added: head/pt_BR.ISO8859-1/articles/committers-guide/article.xml ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/pt_BR.ISO8859-1/articles/committers-guide/article.xml Sun Sep 23 18:41:53 2018 (r52295) @@ -0,0 +1,3056 @@ + + +]> +

+ + + Guia dos Committers + + Projeto de Documenta巽達o do FreeBSD + + 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 Projeto de Documenta巽達o do FreeBSD + + + FreeBSD is a registered trademark of the FreeBSD Foundation. + Coverity is a registered trademark; Coverity Extend, Coverity Prevent and Coverity Prevent SQS are trademarks of Coverity, Inc. + IBM, AIX, OS/2, PowerPC, PS/2, S/390, and ThinkPad are trademarks of International Business Machines Corporation in the United States, other countries, or both. + Intel, Celeron, Centrino, Core, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. + SPARC, SPARC64, and UltraSPARC are trademarks of SPARC International, Inc in the United States and other countries. SPARC International, Inc owns all of the SPARC trademarks and under licensing agreements allows the proper use of these trademarks by its members. + Many of the designations used by manufacturers and sellers to distinguish their products are claimed 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. + + + $FreeBSD$ + + $FreeBSD$ + + + Este documento fornece informa巽探es para a comunidade de committers do FreeBSD. Todos os novos committers devem ler este documento antes de come巽ar, e os committers existentes s達o fortemente encorajados a revis叩-lo de tempos em tempos. + + Quase todos os desenvolvedores do FreeBSD possuem direitos de commit para um ou mais reposit坦rios. No entanto, alguns desenvolvedores n達o tem, e algumas das informa巽探es aqui se aplicam a eles tamb辿m. (Por exemplo, algumas pessoas s坦 t棚m direitos para trabalhar com o banco de dados do Relat坦rio de Problemas). Por favor, veja para mais informa巽探es. + + Este documento tamb辿m pode ser de interesse para os membros da comunidade FreeBSD que querem aprender mais sobre como o projeto funciona. + + + + + Detalhes Administrativos + + + + + + + + M辿todos de login + ssh1 ,_apenas no protocolo 2 + + + + Servidor Principal de Shell + freefall.FreeBSD.org + + + + Raiz do Subversion para o src/ + svn+ssh://repo.FreeBSD.org/base (veja tamb辿m ). + + + + Raiz do Subversion para o doc/ + svn+ssh://repo.FreeBSD.org/doc (veja tamb辿m ). + + + + Raiz do Subversion para o ports/ + + svn+ssh://repo.FreeBSD.org/ports (veja tamb辿m ). + + + + Listas de Discuss達o Internas + developers (tecnicamente chamada de all-developers), doc-developers, doc-committers, ports-developers, ports-committers, src-developers, src-committers. (cada reposit坦rio do projeto tem as suas pr坦prias listas de discuss達o -developers e -committers. Os arquivos destas listas podem ser encontrados nos arquivos /local/mail/repository-name-developers-archive e /local/mail/repository-name-committers-archive no cluster FreeBSD.org.) + + + + + Relat坦rios mensais do Core Team + Dispon鱈veis no diret坦rio /home/core/public/monthly-reports do cluster FreeBSD.org. + + + + Relat坦rios mensais da Equipe de Gest達o do Ports + Dispon鱈veis no diret坦rio /home/portmgr/public/monthly-reports do cluster FreeBSD.org. + + + + Branchs SVN do src/ dignas de aten巽達o + stable/n (n-STABLE), head (-CURRENT) + + + + + + O ssh1 辿 necess叩rio para se conectar aos servidores do projeto. Para mais informa巽探es, veja . + + Links teis: + + + + P叩ginas Internas do Projeto FreeBSD + + + + Servidores do Projeto FreeBSD + + + + Grupos Administrativos do Projeto FreeBSD + + + + + + Chaves Open<acronym>PGP</acronym> para o FreeBSD + + O projeto FreeBSD utiliza chaves criptogr叩ficas em conformidade com o padr達o OpenPGP (Pretty Good Privacy) para autenticar os committers. Mensagens contendo informa巽探es importantes como chaves p炭blicas SSH podem ser assinadas com uma chave OpenPGP para provar que elas vieram realmente do committer. Veja PGP & GPG: Email for the Practical Paranoid by Michael Lucas e para maiores informa巽探es. + + + Criando uma chave + + As chaves existentes podem ser usadas, mas elas devem ser obtidas com o doc/head/share/pgpkeys/checkkey.sh primeiro. + + Para quem ainda n達o tem uma chave OpenPGP, ou precisa de uma nova chave para atender aos requisitos de seguran巽a do FreeBSD, nesta se巽達o iremos mostrar como gerar uma. + + + + + Instale o security/gnupg. Digite estas linhas no ~/.gnupg/gpg.conf para definir padr探es m鱈nimos aceit叩veis: + + fixed-list-mode +keyid-format 0xlong +personal-digest-preferences SHA512 SHA384 SHA256 SHA224 +default-preference-list SHA512 SHA384 SHA256 SHA224 AES256 AES192 AES CAST5 BZIP2 ZLIB ZIP Uncompressed +use-agent +verify-options show-uid-validity +list-options show-uid-validity +sig-notation issuer-fpr@notations.openpgp.fifthhorseman.net=%g +cert-digest-algo SHA512 + + + + Gere uma chave: + + % gpg --full-gen-key +gpg (GnuPG) 2.1.8; Copyright (C) 2015 Free Software Foundation, Inc. +This is free software: you are free to change and redistribute it. +There is NO WARRANTY, to the extent permitted by law. + +Warning: using insecure memory! +Please select what kind of key you want: + (1) RSA and RSA (default) + (2) DSA and Elgamal + (3) DSA (sign only) + (4) RSA (sign only) +Your selection? 1 +RSA keys may be between 1024 and 4096 bits long. +What keysize do you want? (2048) 2048 +Requested keysize is 2048 bits +Please specify how long the key should be valid. + 0 = key does not expire + <n> = key expires in n days + <n>w = key expires in n weeks + <n>m = key expires in n months + <n>y = key expires in n years +Key is valid for? (0) 3y +Key expires at Wed Nov 4 17:20:20 2015 MST +Is this correct? (y/N) y + +GnuPG needs to construct a user ID to identify your key. + +Real name: Chucky Daemon +Email address: notreal@example.com +Comment: +You selected this USER-ID: + "Chucky Daemon <notreal@example.com>" + +Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o +You need a Passphrase to protect your secret key. + + + + Chaves de 2048-bit com uma expira巽達o de 3 anos proveem uma prote巽達o adequada nos dias de hoje (2013-12). O artigo descreve a situa巽達o em mais detalhes. + + + + Tr棚s anos 辿 um tempo de vida para a chave que 辿 curto o suficiente para tornar obsoletas as chaves enfraquecidas pelo avan巽o do poder computacional, mas 辿 tempo suficiente para reduzir os principais problemas de gerenciamento. + + + + Use o seu nome real, preferencialmente o mesmo que consta do seu documento de identifica巽達o (ID) emitido pelo seu governo para tornar mais f叩cil para as outras pessoas confirmarem sua identidade. Voc棚 pode inserir um texto adicional para ajudar outras pessoas a identificar voc棚 na se巽達o Comment. + + + + Depois que o endere巽o de e-mail 辿 inserido, uma senha 辿 solicitada. Os m辿todos de cria巽達o de uma frase secreta segura s達o controversos. Em vez de sugerir um 炭nico caminho, aqui est達o alguns links para sites que descrevem v叩rios m辿todos:, , e . + + + + Proteja a chave privada e a frase secreta. Se a chave privada ou a frase secreta pode ter sido comprometida ou exposta, notifique imediatamente + accounts@FreeBSD.org e revogue a chave. + + O processo para commit da nova chave 辿 mostrado em . + + + + + Kerberos e LDAP Web Password para o cluster do FreeBSD + + O cluster do FreeBSD requer uma senha do Kerberos para acessar certos servi巽os. A senha do Kerberos tamb辿m serve como a senha LDAP para a web, j叩 que o LDAP faz um proxy para o Kerberos no cluster. Alguns dos servi巽os que exigem isso incluem: + + + + Bugzilla + + + Jenkins + + + + Para criar uma nova conta do Kerberos no cluster do FreeBSD, ou para redefinir uma senha do Kerberos para uma conta existente usando um gerador de senha aleat坦ria: + + % ssh kpasswd.freebsd.org + + + Isto deve ser feito a partir de uma m叩quina fora do cluster do FreeBSD.org. + + + Uma senha do Kerberos tamb辿m pode ser definida manualmente, para isto logue no servidor freefall.FreeBSD.org e execute: + + % kpasswd + + + A menos que os servi巽os autenticados por Kerberos do cluster do FreeBSD.org tenham sido usados anteriormente, o erro Client unknownser叩 exibido. Este erro significa que o m辿todo ssh kpasswd.freebsd.org mostrado acima deve ser usado primeiro para inicializar a conta Kerberos. + + + + + + Tipos de Commit Bits + + O reposit坦rio do FreeBSD possui um n炭mero de componentes que, quando combinados, suportam os fontes b叩sicos do sistema operacional, a documenta巽達o, a infraestrutura de ports de aplicativos de terceiros e v叩rios utilit叩rios mantidos. Quando os commit bits do FreeBSD s達o alocados, as 叩reas da 叩rvore onde o bit pode ser usado s達o especificadas. Geralmente, as 叩reas associadas a um bit refletem quem autorizou a aloca巽達o do bit de commit. reas adicionais de autoridade podem ser adicionadas em uma data posterior: quando isso ocorre, o committer deve seguir procedimentos normais de atribui巽達o de bits de confirma巽達o para essa 叩rea da 叩rvore, buscando a aprova巽達o da entidade apropriada e possivelmente obtendo um mentor para essa 叩rea por algum per鱈odo de tempo. + + + + + + Tipo de Committer + Respons叩vel + Componentes da rvore + + + + src + core@ + src/, doc/ sujeito a revis達o apropriada + + + + doc + doceng@ + doc/, ports/, src/ documenta巽達o + + + + ports + portmgr@ + ports/ + + + + + + Os commit bits alocados antes do desenvolvimento da no巽達o de 叩reas de autoridade podem ser apropriados para uso em muitas partes da 叩rvore. No entanto, o senso comum determina que um committer que n達o tenha trabalhado anteriormente em uma 叩rea da 叩rvore busque algu辿m para realizar uma revis達o antes de realizar o commit, busque a aprova巽達o da parte respons叩vel apropriada e/ou trabalhe com um mentor. Uma vez que as regras relativas manuten巽達o de c坦digo diferem por 叩rea da 叩rvore, isso 辿 tanto para o benef鱈cio do committer trabalhando em uma 叩rea de menos familiar quanto para as outras pessoas trabalhando na 叩rvore. + + Committers s達o encorajados a buscar revis達o do seu trabalho como parte do processo normal de desenvolvimento, independentemente da 叩rea da 叩rvore onde o trabalho est叩 ocorrendo. + + + Pol鱈tica para atividade de Committers em outras 叩rvores + + + + Todos os committers podem modificar base/head/share/misc/committers-*.dot, base/head/usr.bin/calendar/calendars/calendar.freebsd, e ports/head/astro/xearth/files. + + + + os doc committers podem efetuar commits de altera巽探es na documenta巽達o sob src, tal como man pages, READMEs, banco de dados do fortune, arquivos de calend叩rios, e comentar corre巽探es sem aprova巽達o de um src committer, sujeito aos cuidados normais necess叩rios para um commit seguro. + + + + Qualquer committer pode fazer altera巽探es em qualquer outra 叩rvore com um "Approved by" de um committer que n達o esteja sob mentoria e que tenha o bit apropriado. + + + + Os committers podem adquirir um bit adicional pelo processo usual de encontrar um mentor que os propor叩 ao core, doceng ou portmgr, conforme apropriado. Quando aprovados, eles ser達o adicionados ao 'access' e o per鱈odo normal de mentoria ir叩 ocorrer, o que envolver叩 a continuidade do uso do Approved by por um per鱈odo. + + + + O "Approved by" s坦 辿 aceit叩vel vindo de src committers que n達o estejam sob mentoria - os committers mentorados podem fornecer um "Reviewed by" mas n達o um "Approved by". + + + + + + + Subversion Primer + + Sup探e-se que novos committers j叩 estejam familiarizados com a opera巽達o b叩sica do Subversion. Se n達o, comece lendo o Subversion Book. + + + Introdu巽達o + + O reposit坦rio de c坦digo fonte do FreeBSD mudou do CVS para o Subversion em 31 de maio de 2008. O primeiro commit real no SVN 辿 o r179447. + + O reposit坦rio do FreeBSD doc/www foi migrado do CVS para o Subversion em 19 de Maio de 2012. O primeiro commit real no SVN foi o r38821. + + O reposit坦rio da cole巽達o de ports do FreeBSD foi migrado do CVS para o Subversion em 14 de Julho 2012. O primeiro commit real no SVN foi o r300894. + + O Subversion pode ser instalado a partir da Cole巽達o de Ports do FreeBSD, executando o comando: + + # pkg install subversion + + + + + Primeiros Passos + + Existem algumas maneiras de obter uma c坦pia de trabalho da 叩rvore do Subversion. Esta se巽達o ir叩 explic叩-las. + + + Checkout direto + + O primeiro 辿 fazer check-out diretamente do reposit坦rio principal. Para a 叩rvore src, use: + + % svn checkout svn+ssh://repo.freebsd.org/base/head /usr/src + + Para a 叩rvore doc, use: + + % svn checkout svn+ssh://repo.freebsd.org/doc/head /usr/doc + + Para a 叩rvore da cole巽達o de ports, use: + + % svn checkout svn+ssh://repo.freebsd.org/ports/head /usr/ports + + + Embora os exemplos restantes neste documento tenham sido escritos tendo o workflow de trabalho com a 叩rvore src em mente, os conceitos b叩sicos s達o os mesmos para se trabalhar com o doc e com a 叩rvore dos ports. Os ports relacionados s opera巽探es do Subversion est達o listados em . + + + O comando acima ir叩 fazer o checkout da 叩rvore de c坦digo-fonte CURRENT como /usr/src/, o qual pode ser qualquer diret坦rio de destino no sistema de arquivos local. Omitir o argumento final desse comando faz com que a c坦pia de trabalho, neste caso, seja nominada como head, mas ela poder叩 ser renomeada com seguran巽a. + + O svn+ssh significa que o protocolo SVN ser叩 tunelado sobre o SSH. O nome do servidor 辿 repo.freebsd.org, e base 辿 o caminho para o reposit坦rio, e head 辿 o subdiret坦rio dentro do reposit坦rio. + + Se seu nome de login no projeto FreeBSD for diferente do nome de login usado na sua m叩quina local, inclua-o na URL (por exemplo svn+ssh://jarjar@repo.freebsd.org/base/head) ou adicione uma entrada no arquivo ~/.ssh/config no formato: + + Host repo.freebsd.org + User jarjar + + Este 辿 o m辿todo mais simples, mas 辿 dif鱈cil dizer quanta carga ele ir叩 colocar no reposit坦rio. + + + O svn diff n達o requer acesso ao servidor pois o SVN armazena uma c坦pia de refer棚ncia de todos os arquivos na c坦pia de trabalho. Isto, no entanto, significa que as c坦pias de trabalho do Subversion s達o muito grandes em tamanho. + + + + + Branches <literal>RELENG_*</literal> e Layout Geral + + No svn+ssh://repo.freebsd.org/base, base refere-se 叩rvore de c坦digo fonte. Similarmente, ports refere-se 叩rvore de ports e assim por diante. Estes s達o reposit坦rios separados com suas pr坦prias seq端棚ncias de n炭meros de mudan巽a, controles de acesso e email de commit. + + Para o reposit坦rio base, HEAD refere-se a 叩rvore -CURRENT. Por exemplo, head/bin/ls 辿 o que entraria como /usr/src/bin/ls em uma release. Alguns locais importantes s達o: + + + + /head/ que corresponde a HEAD, tamb辿m conhecido como -CURRENT. + + + + /stable/n que corresponde a RELENG_n. + + + + /releng/n.n que corresponde a RELENG_n_n. + + + + /release/n.n.n que corresponde a RELENG_n_n_n_RELEASE. + + + + /vendor* 辿 uma 叩rea de trabalho para importar branches de vendors. Este diret坦rio em si n達o cont辿m branches, no entanto, os seus subdiret坦rios cont辿m. Isso contrasta com os diret坦rios stable, releng e release. + + + + /projects e /user s達o 叩reas de trabalho de branch. Como acima, o diret坦rio /user n達o cont辿m branches em si. + + + + + + Branches e Layout do Projeto de Documenta巽達o do FreeBSD + + no svn+ssh://repo.freebsd.org/doc, doc refere-se raiz do reposit坦rio da 叩rvore de c坦digo fonte. + + Em geral, a maior parte do trabalho do Projeto de Documenta巽達o do FreeBSD ser叩 feito dentro do branch head/ da 叩rvore com os arquivos fontes da documenta巽達o. + + A documenta巽達o do FreeBSD 辿 escrita e/ou traduzida para v叩rios idiomas, cada um em um diret坦rio separado no branch head/. + + Cada conjunto de tradu巽達o cont辿m v叩rios subdiret坦rios para as v叩rias partes do Projeto de Documenta巽達o do FreeBSD. Alguns diret坦rios not叩veis s達o: + + + + /articles/ cont辿m o c坦digo fonte para artigos escritos por v叩rios colaboradores do FreeBSD. + + + + /books/ cont辿m o c坦digo fonte para os diferentes livros, como o Handbook do FreeBSD. + + + + /htdocs/ cont辿m o c坦digo-fonte do website do FreeBSD. + + + + + + Branches e Layout da rvore de Ports do FreeBSD + + No svn+ssh: //repo.freebsd.org/ports, ports refere-se raiz do reposit坦rio da 叩rvore de ports. + + Em geral, a maior parte do trabalho na cole巽達o de ports do FreeBSD ser叩 feito dentro da branch head/ da 叩rvore de ports, que 辿 a 叩rvore de ports real usada para instalar software. Alguns outros locais importantes s達o: + + + + /branches/RELENG_n_n_n que corresponde a RELENG_n_n_n e 辿 usado para mesclar atualiza巽探es de seguran巽a em prepara巽達o para uma release. + + + + /tags/RELEASE_n_n_n que corresponde a RELEASE_n_n_n e representa uma tag de release da 叩rvore de ports. + + + + /tags/RELEASE_n_EOL representa o tag de end of life de um branch espec鱈fico do FreeBSD. + + + + + + + Uso di叩rio + + Esta se巽達o explicar叩 como realizar opera巽探es comuns do dia-a-dia com o Subversion. + + + Ajuda + + O SVN traz em si uma documenta巽達o interna de ajuda. Ela pode ser acessada digitando: + + % svn help + + Informa巽探es adicionais podem ser encontradas no Subversion Book. + + + + Checkout + + Como visto anteriormente, para fazer o checkout da branch principal (head) do FreeBSD: + + % svn checkout svn+ssh://repo.freebsd.org/base/head /usr/src + + Em algum momento, provavelmente ser叩 炭til ter uma copia de trabalho mais do que apenas do HEAD, por exemplo, ao mesclar as altera巽探es para stable/7. Portanto, pode ser 炭til ter uma verifica巽達o parcial da 叩rvore completa (um check-out completo seria muito doloroso). + + Para fazer isso, primeiro confira a raiz do reposit坦rio: + + % svn checkout --depth=immediates svn+ssh://repo.freebsd.org/base + + Isso vai obter o base com todos os arquivos que ele cont辿m (no momento da escrita, apenas o ROADMAP.txt) e subdiret坦rios vazios para head, stable, vendor e assim por diante. + + poss鱈vel expandir a c坦pia de trabalho. Basta alterar a profundidade dos v叩rios subdiret坦rios: + + % svn up --set-depth=infinity base/head +% svn up --set-depth=immediates base/release base/releng base/stable + + O comando acima ir叩 baixar uma c坦pia completa do head, al辿m de c坦pias vazias de cada tag de release, de cada branch de releng, e de cada branch stable. + + Se numa data posterior voc棚 tiver necessidade de mesclar algo, por exemplo, com a 7-STABLE, expanda a c坦pia de trabalho: + + % svn up --set-depth=infinity base/stable/7 + + As sub叩rvores n達o precisam ser expandidas completamente. Por exemplo, para expandir apenas o stable/7/sys e depois expandir o resto do stable/7: + + % svn up --set-depth=infinity base/stable/7/sys +% svn up --set-depth=infinity base/stable/7 + + Atualizar a 叩rvore com svn update ir叩 apenas atualizar o que foi pedido anteriormente (neste caso, head e stable/7), ele n達o ir叩 puxar a 叩rvore inteira. + + + + Checkout Anonimo + + poss鱈vel efetuar o checkout anonimo o reposit坦rio Subversion do FreeBSD. Isso dar叩 acesso a uma 叩rvore somente leitura que pode ser atualizada, mas que n達o poder叩 ser enviada de volta para o reposit坦rio principal por meio de um commit. Para fazer isso, use: + + % svn co https://svn.FreeBSD.org/base/head /usr/src + + Mais detalhes sobre o uso do Subversion podem ser encontrados emUsando o Subversion. + + + + Atualizando a rvore + + Para atualizar uma c坦pia de trabalho para a revis達o mais recente ou uma revis達o espec鱈fica: + + % svn update +% svn update -r12345 + + + + Status + + Para ver as altera巽探es locais que foram feitas na c坦pia de trabalho: + + % svn status + + Para mostrar altera巽探es locais e arquivos que est達o desatualizados, execute: + + % svn status --show-updates + + + + Editando e efetuando o commit + + O SVN n達o precisa ser avisado com anteced棚ncia sobre a edi巽達o de arquivos. + + Para efetuar o commit de todas as altera巽探es no diret坦rio atual e em todos os seus subdiret坦rios: + + % svn commit + + Para efetuar o commit de todas as altera巽探es, por exemplo, nos arquivos lib/libfetch/ e usr/bin/fetch/ em uma 炭nica opera巽達o, execute: + + % svn commit lib/libfetch usr/bin/fetch + + Tamb辿m existe um wrapper de commit para a 叩rvore de ports para manipular as propriedades e para verificar a sanidade das mudan巽as: + + % /usr/ports/Tools/scripts/psvn commit + + + + Adicionando e Removendo Arquivos + + + Antes de adicionar arquivos, obtenha uma c坦pia do auto-props.txt (h叩 tamb辿m um vers達o espec鱈fica da 叩rvore de ports) e adicione-o ao ~/.subversion/config seguindo as instru巽探es contidas no arquivo. Se voc棚 adicionou algo antes de ler isto, use o comando svn rm --keep-local para apenas os arquivos adicionados, corrija seu arquivo de configura巽達o e adicione-os novamente. O arquivo de configura巽達o inicial 辿 criado quando voc棚 executa um comando svn pela primeira vez, at辿 mesmo algo t達o simples quanto svn help. + + + Os arquivos s達o adicionados a um SVN reposit坦rio com svn add. Para adicionar um arquivo chamado foo, edite-o e depois execute: + + % svn add foo + + + A maioria dos novos arquivos fonte deve incluir uma string $FreeBSD$ pr坦xima ao in鱈cio do arquivo. Ao efetuar o commit, o svn expandir叩 a string $FreeBSD$, adicionando o caminho do arquivo, o n炭mero da revis達o, a data e a hora da confirma巽達o e o nome de usu叩rio do committer. Arquivos que n達o podem ser modificados podem ser enviados sem a string $FreeBSD$. + + + Os arquivos podem ser removidos com svn remove: + + % svn remove foo + + O subversion n達o requer a exclus達o do arquivo antes de usaramos o comando svn rm e, de fato, ele reclama se isso acontecer. + + poss鱈vel adicionar diret坦rios com svn add: + + % mkdir bar +% svn add bar + + Apesar que o svn mkdir torna isso mais f叩cil, combinando a cria巽達o do diret坦rio e a adi巽達o dele: + + % svn mkdir bar + + Como arquivos, os diret坦rios s達o removidos com svn rm. N達o existe um comando separado especificamente para remover diret坦rios. + + % svn rm bar + + + + Copiando e Movendo Arquivos + + Este comando cria uma c坦pia do arquivo foo.c nomeado bar.c, com o novo arquivo tamb辿m sob controle de vers達o e com o hist坦rico completo de foo.c: + + % svn copy foo.c bar.c + + Geralmente 辿 prefer鱈vel copiar desta forma ao inv辿s de copiar o arquivo com comando cp e adicionando-o ao reposit坦rio com svn add porque desta forma o novo arquivo n達o herda a hist坦ria do original. + + Para mover e renomear um arquivo: + + % svn move foo.c bar.c + + + + Logs e Anota巽探es + + O svn log mostra revis探es e mensagens de commit, as mais recentes s達o exibidas primeiro, para arquivos ou diret坦rios. Quando usado em um diret坦rio, todas as revis探es que afetaram o diret坦rio e os arquivos nesse diret坦rio s達o mostradas. + + O svn annotate , ou igualmente o svn praise ou svn blame, mostra o n炭mero de revis達o mais recente e quem fez o commit dessa revis達o para cada linha de um arquivo. + + + + Diffs + + O svn diff exibe altera巽探es na c坦pia de trabalho. Diffs gerado por SVN s達o unificados e incluem novos arquivos por padr達o na sa鱈da do diff. + + O svn diff pode mostrar as mudan巽as entre duas revis探es do mesmo arquivo: + + % svn diff -r179453:179454 ROADMAP.txt + + Ele tamb辿m pode mostrar todas as altera巽探es para um changeset espec鱈fico. Este comando mostra quais altera巽探es foram feitas no diret坦rio atual e em todos os subdiret坦rios do changeset 179454: + + % svn diff -c179454 . + + + + Revertendo + + Mudan巽as locais (incluindo adi巽探es e dele巽探es) podem ser revertidas usando svn revert. Ele n達o atualiza arquivos desatualizados, apenas os substitui por c坦pias originais da vers達o original. + + + + Conflitos + + Se um svn update resultou em um conflito de mesclagem, o Subversion ir叩 lembrar quais arquivos t棚m conflitos e se recusar叩 a fazer o commit de quaisquer altera巽探es nesses arquivos at辿 que seja explicitamente informado que os conflitos foram resolvidos. O procedimento simples, ainda n達o obsoleto, 辿: + + % svn resolved foo + + No entanto, o procedimento preferido 辿: + + % svn resolve --accept=working foo + + Os dois exemplos s達o equivalentes. Os valores poss鱈veis para --accept s達o: + + + + working: use a vers達o em seu diret坦rio de trabalho (a qual se presume que foi editada para resolver os conflitos). + + + + base: usar uma c坦pia original da vers達o que voc棚 tinha antes do svn update, descartando suas pr坦prias altera巽探es, as mudan巽as conflitantes e possivelmente outras mudan巽as intervenientes tamb辿m. + + + + mine-full: use o que voc棚 tinha antes do svn update, incluindo suas pr坦prias mudan巽as, mas descartando as mudan巽as conflitantes, e possivelmente outras mudan巽as intervenientes tamb辿m. + + + + theirs-full: use a vers達o que foi recuperada quando voc棚 fez o svn update, descartando as suas pr坦prias mudan巽as. + + + + + + + Uso Avan巽ado + + + Checkouts dispersos + + O SVN permite sparse, ou checkouts parciais de um diret坦rio adicionando a um svn checkout. + + Os argumentos v叩lidos para s達o: + + + + empty: o pr坦prio diret坦rio sem qualquer conte炭do. + + + + files: o diret坦rio e quaisquer arquivos nele contidos. + + + + immediates: o diret坦rio e quaisquer arquivos e diret坦rios contidos nele, mas nenhum dos conte炭dos dos subdiret坦rios. + + + + infinity: qualquer coisa. + + + + A op巽達o --depth se aplica a muitos outros comandos, incluindo svn commit, svn revert e o svn diff. + + Como o par但metro --depth utilizado 辿 persistente, existe uma op巽達o --set-depth para o svn update que ir叩 mudar a profundidade selecionada. Assim, dada a c坦pia de trabalho produzida pelo exemplo anterior: + + % cd ~/freebsd +% svn update --set-depth=immediates . + + O comando acima ir叩 popular a c坦pia de trabalho em ~/freebsd com ROADMAP.txt e subdiret坦rios vazios, e nada acontecer叩 quando svn update for executado nos subdiret坦rios. No entanto, esse comando definir叩 a profundidade para head (nesse caso) como infinito e o popular叩 totalmente: + + % svn update --set-depth=infinity head + + + + Opera巽達o Direta + + Certas opera巽探es podem ser realizadas diretamente no reposit坦rio sem tocar na c坦pia de trabalho. Especificamente, isso se aplica a qualquer opera巽達o que n達o exija a edi巽達o de um arquivo, incluindo: + + + + log, diff + + + + mkdir + + + + remove, copy, rename + + + + propset, propedit, propdel + + + + merge + + + + A cria巽達o de uma branch 辿 muito r叩pida. Este comando seria usado para criar a branch RELENG_8: + + % svn copy svn+ssh://repo.freebsd.org/base/head svn+ssh://repo.freebsd.org/base/stable/8 + + Isso equivale a esses comandos, que levam minutos e horas, em vez de segundos, dependendo da sua conex達o de rede: + + % svn checkout --depth=immediates svn+ssh://repo.freebsd.org/base +% cd base +% svn update --set-depth=infinity head +% svn copy head stable/8 +% svn commit stable/8 + + + + Mesclando com <acronym>SVN</acronym> + + Esta se巽達o lida com o merge de c坦digo de um branch para outro (normalmente, do head para um brach stable). + + + Em todos os exemplos abaixo, $FSVN refere-se localiza巽達o do reposit坦rio Subversion do FreeBSD, svn+ssh://repo.freebsd.org/base . + + + + Sobre o acompanhamento de mesclagem + + Do ponto de vista do usu叩rio, informa巽探es de acompanhamento de mesclagem (ou mergeinfo) s達o armazenadas em uma propriedade chamada svn:mergeinfo, que 辿 uma lista separada por v鱈rgulas de revis探es e intervalos de revis探es que foram mescladas. Quando definido em um arquivo, ele se aplica somente a esse arquivo. Quando definido em um diret坦rio, ele se aplica a esse diret坦rio e seus descendentes (arquivos e diret坦rios), exceto aqueles que possuem o seu pr坦prio svn:mergeinfo. + + Ele n達o 辿 herdado. Por exemplo, stable/6/contrib/openpam/ n達o herda implicitamente o mergeinfo de stable/6/, ou do stable/6/contrib/. Isso faria com que os checkouts parciais fossem dif鱈ceis de gerenciar. Em vez disso, o mergeinfo 辿 explicitamente propagado pela 叩rvore. Para mesclar algo em branch/foo/bar/, estas regras se aplicam: + + + + Se branch/foo/bar/ ainda n達o tiver um registro mergeinfo, mas um ancestral direto (por exemplo, branch/foo/) tem, ent達o esse registro ser叩 propagado para abaixo at辿 branch/foo/bar/ antes que as informa巽探es sobre a mesclagem atual sejam registradas. + + + + As informa巽探es sobre a mesclagem atual n達o ser達o propagadas para o ancestral. + + + + Se um descendente direto de branch/foo/bar/ (por exemplo, branch/foo/bar/baz/) j叩 tiver um registro mergeinfo, as informa巽探es sobre a mesclagem atual ser達o propagadas para ele. + + + + Se voc棚 considerar o caso em que uma revis達o altera v叩rias partes separadas da 叩rvore (por exemplo, branch/foo/bar/ e branch/foo/quux/), mas voc棚 s坦 deseja mesclar alguns deles (por exemplo, branch/foo/bar/), voc棚 ver叩 que essas regras fazem sentido. Se mergeinfo fosse propagado, pareceria que a revis達o tamb辿m foi mesclada com branch/foo/quux/, quando na verdade n達o foi. + + + + Selecionando a branch de origem e de destino ao mesclar + + Mesclagens para as branches stable/ devem originar-se da head/. Por exemplo: + + % svn merge -c r123456 ^/head/ stable/11 +% svn commit stable/11 + + Mesclagens para as branches releng/ devem sempre se originar da branch stable/ correspondente. Por exemplo: + + % svn merge -c r123456 ^/stable/11 releng/11.0 +% svn commit releng/11.0 + + + Os committers s坦 podem se efetuar um commit para as branches releng/ durante um ciclo de release ap坦s receber aprova巽達o da Equipe de Engenharia de Release, ap坦s o qual somente o Security Officer pode efetuar commits para o branch releng/ para um Aviso de Seguran巽a ou Aviso de Errata. + + + Todas as mesclagens s達o mescladas e enviadas por commit a partir da raiz da branch. Todas as mesclagens se parecem com: + + % svn merge -c r123456 ^/head/ checkout +% svn commit checkout + + Observe que checkout deve ser uma verifica巽達o completa da branch na qual a mesclagem ocorre. + + % svn merge -c r123456 ^/stable/10 releng/10.0 + + + + Preparando o Alvo de Mesclagem (Merge Target) + + Devido aos problemas de propaga巽達o do mergeinfo descritos anteriormente, 辿 muito importante nunca mesclar as altera巽探es em uma c坦pia de trabalho esparsa. Sempre use um checkout completo do branch que est叩 sendo mesclado. Por exemplo, ao mesclar de HEAD para 7, use um checkout completo de stable/7: + + % cd stable/7 +% svn up --set-depth=infinity + + O diret坦rio de destino tamb辿m deve estar atualizado e n達o deve conter altera巽探es que ainda n達o foram enviadas por commit ou arquivos perdidos. + + + + Identificando Revis探es + + Identificar revis探es a serem mescladas 辿 uma obriga巽達o. Se o alvo j叩 tiver mergeinfo completo, solicite uma lista para o SVN: + + % cd stable/6/contrib/openpam +% svn mergeinfo --show-revs=eligible $FSVN/head/contrib/openpam + + Se o destino n達o tiver mergeinfo completo, verifique o log da origem de mesclagem. + + + + Mesclando + + Agora vamos come巽ar a mesclar! + + + Os princ鱈pios + + Por exemplo, para mesclar: + + + + revis達o $R + + + + no diret坦rio $target na branch stable $B + + + + a partir do diret坦rio $source no head + + + + $FSVN 辿 o svn+ssh://repo.freebsd.org/base + + + + Supondo que as revis探es $P e $Q j叩 tenham sido mescladas e que o diret坦rio atual seja uma c坦pia de trabalho atualizada de stable/$B, a mergeinfo existente ser叩 semelhante a: + + % svn propget svn:mergeinfo -R $target +$target - /head/$source:$P,$Q + + A mesclagem 辿 feita assim: + + % svn merge -c$R $FSVN/head/$source $target + + poss鱈vel verificar os resultados disso com um svn diff. + + O svn:mergeinfo agora se parece com: + + % svn propget svn:mergeinfo -R $target +$target - head/$source:$P,$Q,$R + + Se os resultados n達o forem exatamente como os mostrados, voc棚 pode precisar de assist棚ncia antes de efetuar o commit pois erros podem ter sido cometidos, ou pode haver algo errado com o mergeinfo existente, ou pode haver um bug no Subversion. + + + + Exemplo Pr叩tico + + Como um exemplo pr叩tico, considere este cen叩rio. As altera巽探es no netmap.4 no r238987 devem ser mescladas do CURRENT para o 9-STABLE. O arquivo reside em head/share/man/man4. De acordo com o , tamb辿m 辿 onde devemos fazer a mesclagem. Note que neste exemplo todos os caminhos s達o relativos ao topo do reposit坦rio svn. Para obter mais informa巽探es sobre o layout do diret坦rio, consulte . + + O primeiro passo 辿 inspecionar o mergeinfo existente. + + % svn propget svn:mergeinfo -R stable/9/share/man/man4 + + Tome uma nota r叩pida de como ele se parece antes de avan巽ar para o pr坦ximo passo; fazendo a mesclagem real: + + % svn merge -c r238987 svn+ssh://repo.freebsd.org/base/head/share/man/man4 stable/9/share/man/man4 +--- Merging r238987 into 'stable/9/share/man/man4': +U stable/9/share/man/man4/netmap.4 +--- Recording mergeinfo for merge of r238987 into +'stable/9/share/man/man4': + U stable/9/share/man/man4 + + Verifique se o n炭mero de revis達o da revis達o mesclada foi adicionado. Quando isso for verificado, a 炭nica coisa que resta 辿 o commit em si. + + % svn commit stable/9/share/man/man4 + + + + + Precau巽探es antes de efetuar o commit + + Como sempre, fa巽a um build world (ou as partes apropriadas dele). + + Verifique as mudan巽as com o svn diff e svn stat. Certifique-se de que todos os arquivos que deveriam ter sido adicionados ou exclu鱈dos foram de fato adicionados ou exclu鱈dos. + + D棚 uma olhada mais de perto em qualquer mudan巽a de propriedade (marcada por um M na segunda coluna do svn stat). Normalmente, nenhuma propriedade svn:mergeinfo deve estar em qualquer lugar, exceto o diret坦rio (ou diret坦rios) de destino. + + Se algo parecer suspeito, pe巽a ajuda. + + + + Fazendo o commit + + Certifique-se de efetuar o commit de um diret坦rio de n鱈vel superior para incluir tamb辿m o mergeinfo. N達o especifique arquivos individuais na linha de comando. Para mais informa巽探es sobre como submeter arquivos em geral, veja a se巽達o relevante deste manual. + + + + + Importa巽探es de fornecedores com <acronym>SVN</acronym> + + + Por favor, leia toda esta se巽達o antes de iniciar uma importa巽達o de fornecedores. + + + + Os patches para o c坦digo do fornecedor se enquadram em duas categorias: + + + + Patches do fornecedor: s達o patches que foram emitidos pelo fornecedor ou que foram extra鱈dos do sistema de controle de vers達o do fornecedor, que abordam problemas que n達o podem esperar at辿 a pr坦xima vers達o do fornecedor. + + + + Patches do FreeBSD: s達o patches que modificam o c坦digo do fornecedor para resolver problemas espec鱈ficos do FreeBSD. + + + + A natureza de um patch determina para onde ele deve ser enviado por commit: + + + + Os patches do fornecedor devem ser enviados por commit para o branch do fornecedor e mesclados a partir dele. Se o patch resolver um problema em uma nova vers達o que est叩 sendo importada atualmente, ele n達o deve ser enviado por commit junto com a nova vers達o: a vers達o deve ser importada e marcada primeiro, ent達o a corre巽達o pode ser aplicada e o commit efetuado. N達o h叩 necessidade de marcar novamente as fontes do fornecedor depois de confirmar o patch. + + + + Patches do FreeBSD s達o enviados diretamente para o head. + + + + + + Preparando a rvore + + Se estiver importando pela primeira vez ap坦s a mudan巽a para o Subversion, 辿 necess叩rio achatar e limpar a 叩rvore do fornecedor, bem como inicializar o hist坦rico de mesclagem na 叩rvore principal. + + + Achatamento + + Durante a convers達o do CVS para o Subversion, as branches do fornecedor foram importadas com o mesmo layout da 叩rvore principal. Isso significa que as fontes do fornecedor pf foram armazenadas originalmente em vendor/pf/dist/contrib/pf. O c坦digo fonte do fornecedor fica melhor se armazenado diretamente em vendor/pf/dist. + + Para achatar a 叩rvore do pf: + + % cd vendor/pf/dist/contrib/pf +% svn mv $(svn list) ../.. +% cd ../.. +% svn rm contrib +% svn propdel -R svn:mergeinfo . +% svn commit + + O bit propdel 辿 necess叩rio porque, come巽ando com 1.5, o Subversion adicionar叩 svn:mergeinfo em qualquer diret坦rio que seja copiado ou movido. Nesse caso, como nada est叩 sendo mesclado da 叩rvore exclu鱈da, eles apenas atrapalham. + + As tags tamb辿m podem ser achatadas (3, 4, 3.5 etc.); o procedimento 辿 exatamente o mesmo, mudando apenas dist para 3.5 ou similar, e aguardando para executar o svn commit apenas no final do processo. *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-head@freebsd.org Mon Sep 24 09:34:56 2018 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A1BBE10A765B; Mon, 24 Sep 2018 09:34:55 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 55C9A769C0; Mon, 24 Sep 2018 09:34:55 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 32255179FD; Mon, 24 Sep 2018 09:34:55 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w8O9Ytxv074453; Mon, 24 Sep 2018 09:34:55 GMT (envelope-from bcr@FreeBSD.org) Received: (from bcr@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w8O9YtVH074452; Mon, 24 Sep 2018 09:34:55 GMT (envelope-from bcr@FreeBSD.org) Message-Id: <201809240934.w8O9YtVH074452@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bcr set sender to bcr@FreeBSD.org using -f From: Benedict Reuschling Date: Mon, 24 Sep 2018 09:34:55 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52296 - head/en_US.ISO8859-1/articles/hubs X-SVN-Group: doc-head X-SVN-Commit-Author: bcr X-SVN-Commit-Paths: head/en_US.ISO8859-1/articles/hubs X-SVN-Commit-Revision: 52296 X-SVN-Commit-Repository: doc 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.27 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2018 09:34:56 -0000 Author: bcr Date: Mon Sep 24 09:34:54 2018 New Revision: 52296 URL: https://svnweb.freebsd.org/changeset/doc/52296 Log: Clean up the article from textproc/igor warnings such as: - wrap long lines - use tabs instead of spaces - capitalization - put content after tags - leave a blank line after tags - use two spaces at sentence start Modified: head/en_US.ISO8859-1/articles/hubs/article.xml Modified: head/en_US.ISO8859-1/articles/hubs/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/hubs/article.xml Sun Sep 23 18:41:53 2018 (r52295) +++ head/en_US.ISO8859-1/articles/hubs/article.xml Mon Sep 24 09:34:54 2018 (r52296) @@ -1,22 +1,57 @@ <?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN" "http://www.FreeBSD.org/XML/share/xml/freebsd50.dtd"> -<article xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en"> - <info><title>Mirroring FreeBSD - +
+ + Mirroring FreeBSD + - JunKuriyama -
kuriyama@FreeBSD.org
- - ValentinoVaschetto -
logo@FreeBSD.org
- - DanielLang -
dl@leo.org
- - KenSmith -
kensmith@FreeBSD.org
- + + + Jun + Kuriyama + + +
+ kuriyama@FreeBSD.org +
+ + + + + Valentino + Vaschetto + + +
+ logo@FreeBSD.org +
+ + + + + Daniel + Lang + + +
+ dl@leo.org +
+ + + + + Ken + Smith + + +
+ kensmith@FreeBSD.org +
+ + @@ -30,7 +65,7 @@ An in-progress article on how to mirror FreeBSD, aimed at - hub administrators. + hub administrators. @@ -47,662 +82,723 @@ - Requirements for FreeBSD mirrors + Requirements for FreeBSD Mirrors + Disk Space - - Disk space is one of the most important requirements. - Depending on the set of releases, architectures, - and degree of completeness you want to mirror, a huge - amount of disk space may be consumed. Also keep in mind - that official mirrors are probably required to be - complete. The web pages should - always be mirrored completely. Also note that the - numbers stated here are reflecting the current - state (at &rel2.current;-RELEASE/&rel.current;-RELEASE). Further development and - releases will only increase the required amount. - Also make sure to keep some (ca. 10-20%) extra space - around just to be sure. - Here are some approximate figures: - + + Disk space is one of the most important requirements. + Depending on the set of releases, architectures, and degree of + completeness you want to mirror, a huge amount of disk space + may be consumed. Also keep in mind that + official mirrors are probably required to + be complete. The web pages should always be mirrored + completely. Also note that the numbers stated here are + reflecting the current state (at + &rel2.current;-RELEASE/&rel.current;-RELEASE). Further + development and releases will only increase the required + amount. Also make sure to keep some (ca. 10-20%) extra space + around just to be sure. Here are some approximate + figures: + - Full FTP Distribution: 1.4 TB - CTM deltas: 10 GB - Web pages: 1GB + + Full FTP Distribution: 1.4 TB + + + CTM deltas: 10 GB + + + Web pages: 1GB + - - The current disk usage of FTP Distribution can be found at - ftp://ftp.FreeBSD.org/pub/FreeBSD/dir.sizes. - + + The current disk usage of FTP Distribution can be found at + ftp://ftp.FreeBSD.org/pub/FreeBSD/dir.sizes. Network Connection/Bandwidth - - Of course, you need to be connected to the Internet. - The required bandwidth depends on your intended use - of the mirror. If you just want to mirror some - parts of FreeBSD for local use at your site/intranet, - the demand may be much smaller than if you want to - make the files publicly available. If you intend - to become an official mirror, the bandwidth required will be even higher. We can only give rough - estimates here: - + + Of course, you need to be connected to the Internet. The + required bandwidth depends on your intended use of the mirror. + If you just want to mirror some parts of FreeBSD for local use + at your site/intranet, the demand may be much smaller than if + you want to make the files publicly available. If you intend + to become an official mirror, the bandwidth required will be + even higher. We can only give rough estimates here: + - Local site, no public access: basically no minimum, - but < 2 Mbps could make syncing too slow. - Unofficial public site: 34 Mbps is probably a good start. - Official site: > 100 Mbps is recommended, and your host - should be connected as close as possible to your border router. + + Local site, no public access: basically no minimum, + but < 2 Mbps could make syncing too + slow. + + + + Unofficial public site: 34 Mbps is probably a good + start. + + + + Official site: > 100 Mbps is recommended, and your + host should be connected as close as possible to your + border router. + + System Requirements, CPU, RAM - - One thing this depends on the expected number of clients, - which is determined by the server's policy. It is - also affected by the types of services you want to offer. - Plain FTP or HTTP services may not require a huge - amount of resources. Watch out if you provide - rsync. This can have a huge - impact on CPU and memory requirements as it is - considered a memory hog. - The following - are just examples to give you a very rough hint. - - - For a moderately visited site that offers - rsync, you might - consider a current CPU with around 800MHz - 1 GHz, - and at least 512MB RAM. This is probably the - minimum you want for an official - site. - - - For a frequently used site you definitely need - more RAM (consider 2GB as a good start) - and possibly more CPU, which could also mean - that you need to go for a SMP system. - - - You also want to consider a fast disk subsystem. - Operations on the SVN repository require a fast - disk subsystem (RAID is highly advised). A SCSI - controller that has a cache of its own can also - speed up things since most of these services incur a - large number of small modifications to the disk. - + + One thing this depends on the expected number of clients, + which is determined by the server's policy. It is also + affected by the types of services you want to offer. Plain + FTP or HTTP services may not require a huge amount of + resources. Watch out if you provide rsync. This can have a + huge impact on CPU and memory requirements as it is considered + a memory hog. The following are just examples to give you a + very rough hint. + + For a moderately visited site that offers + rsync, you might consider a current + CPU with around 800MHz - 1 GHz, and at least 512MB RAM. This + is probably the minimum you want for an + official site. + + For a frequently used site you definitely need more RAM + (consider 2GB as a good start) and possibly more CPU, which + could also mean that you need to go for a SMP system. + + You also want to consider a fast disk subsystem. + Operations on the SVN repository require a fast disk subsystem + (RAID is highly advised). A SCSI controller that has a cache + of its own can also speed up things since most of these + services incur a large number of small modifications to the + disk. + - Services to offer - - Every mirror site is required to have a set of core services - available. In addition to these required services, there are - a number of optional services that - server administrators may choose to offer. This section explains - which services you can provide and how to go about implementing them. - + Services to Offer + + Every mirror site is required to have a set of core + services available. In addition to these required services, + there are a number of optional services that server + administrators may choose to offer. This section explains + which services you can provide and how to go about + implementing them. + - FTP (required for FTP fileset) - - This is one of the most basic services, and - it is required for each mirror offering public - FTP distributions. FTP access must be - anonymous, and no upload/download ratios - are allowed (a ridiculous thing anyway). - Upload capability is not required (and must - never be allowed for the FreeBSD file space). - Also the FreeBSD archive should be available under - the path /pub/FreeBSD. - - - There is a lot of software available which - can be set up to allow anonymous FTP - (in alphabetical order). - - /usr/libexec/ftpd: FreeBSD's own ftpd - can be used. Be sure to read &man.ftpd.8;. - - - ftp/ncftpd: A commercial package, - free for educational use. - - - ftp/oftpd: An ftpd designed with - security as a main focus. - - - ftp/proftpd: A modular and very flexible ftpd. - - - ftp/pure-ftpd: Another ftpd developed with - security in mind. - - ftp/twoftpd: As above. - ftp/vsftpd: The very secure ftpd. - - FreeBSD's ftpd, proftpd - and maybe ncftpd - are among the most commonly used FTPds. - The others do not have a large userbase among mirror sites. One - thing to consider is that you may need flexibility in limiting - how many simultaneous connections are allowed, thus limiting how - much network bandwidth and system resources are consumed. - + FTP (required for FTP Fileset) + + This is one of the most basic services, and it is + required for each mirror offering public FTP distributions. + FTP access must be anonymous, and no upload/download ratios + are allowed (a ridiculous thing anyway). Upload capability + is not required (and must never be + allowed for the FreeBSD file space). Also the FreeBSD + archive should be available under the path + /pub/FreeBSD. + + There is a lot of software available which can be set up + to allow anonymous FTP (in alphabetical order). + + + + /usr/libexec/ftpd: FreeBSD's own + ftpd can be used. Be sure to read &man.ftpd.8;. + + + + ftp/ncftpd: A commercial package, + free for educational use. + + + + ftp/oftpd: An ftpd designed with + security as a main focus. + + + + ftp/proftpd: A modular and very + flexible ftpd. + + + + ftp/pure-ftpd: Another ftpd + developed with security in mind. + + + + ftp/twoftpd: As + above. + + + + ftp/vsftpd: The very + secure ftpd. + + + + FreeBSD's ftpd, + proftpd and maybe + ncftpd are among the most + commonly used FTPds. The others do not have a large + userbase among mirror sites. One thing to consider is that + you may need flexibility in limiting how many simultaneous + connections are allowed, thus limiting how much network + bandwidth and system resources are consumed. + - Rsync (optional for FTP fileset) - - Rsync is often offered for access to the - contents of the FTP area of FreeBSD, so other mirror sites can use your system as their source. The - protocol is different from FTP in many ways. - It is much more - bandwidth friendly, as only differences between files - are transferred instead of whole files when they change. - Rsync does require a significant amount of memory for - each instance. The size depends on the size of - the synced module in terms of the number of directories and - files. Rsync can use rsh and - ssh (now default) as a transport, - or use its own protocol for stand-alone access - (this is the preferred method for public rsync servers). - Authentication, connection limits, and other restrictions - may be applied. There is just one software package - available: - - net/rsync - + Rsync (optional for FTP Fileset) + + Rsync is often offered for + access to the contents of the FTP area of FreeBSD, so other + mirror sites can use your system as their source. The + protocol is different from FTP in many ways. It is much + more bandwidth friendly, as only differences between files + are transferred instead of whole files when they change. + Rsync does require a significant + amount of memory for each instance. The size depends on the + size of the synced module in terms of the number of + directories and files. Rsync can + use rsh and ssh (now + default) as a transport, or use its own protocol for + stand-alone access (this is the preferred method for public + rsync servers). Authentication, connection limits, and + other restrictions may be applied. There is just one + software package available: + + + + net/rsync + + + - HTTP (required for web pages, optional for FTP fileset) - - If you want to offer the FreeBSD web pages, you will need - to install a web server. - You may optionally offer the FTP fileset via HTTP. - The choice of web server software is left up to the mirror administrator. - Some of the most popular choices are: + HTTP (required for Web Pages, Optional for FTP + Fileset) - - - www/apache24: - Apache is still one of the most widely - deployed web servers on the Internet. It is used - extensively by the FreeBSD Project. - + If you want to offer the FreeBSD web pages, you will + need to install a web server. You may optionally offer the + FTP fileset via HTTP. The choice of web server software is + left up to the mirror administrator. Some of the most + popular choices are: - - www/boa: - Boa is a single-tasking HTTP server. - Unlike traditional web servers, it does not fork for each incoming - connection, nor does it fork many copies of itself to handle multiple - connections. Although, it should provide considerably great - performance for purely static content. - + + + www/apache24: + Apache is still one of the + most widely deployed web servers on the Internet. It is + used extensively by the FreeBSD Project. + - - www/cherokee: - >Cherokee is a very fast, flexible and - easy to configure web server. It supports the widespread technologies - nowadays: FastCGI, SCGI, PHP, CGI, SSL/TLS encrypted connections, - vhosts, users authentication, on the fly encoding and load balancing. - It also generates Apache compatible log - files. - + + www/boa: + Boa is a single-tasking HTTP + server. Unlike traditional web servers, it does not + fork for each incoming connection, nor does it fork many + copies of itself to handle multiple connections. + Although, it should provide considerably great + performance for purely static content. + - - www/lighttpd: - lighttpd is a secure, fast, compliant and - very flexible web server which has been optimized for high-performance - environments. It has a very low memory footprint compared to other web - servers and takes care of cpu-load. - + + www/cherokee: + >Cherokee is a very fast, + flexible and easy to configure web server. It supports + the widespread technologies nowadays: FastCGI, SCGI, + PHP, CGI, SSL/TLS encrypted connections, vhosts, users + authentication, on the fly encoding and load balancing. + It also generates Apache + compatible log files. + - - www/nginx: - nginx is a high performance edge web - server with a low memory footprint and key features to build - a modern and efficient web infrastructure. Features include - a HTTP server, HTTP and mail reverse proxy, caching, load - balancing, compression, request throttling, connection - multiplexing and reuse, SSL offload and HTTP media - streaming. - + + www/lighttpd: + lighttpd is a secure, fast, + compliant and very flexible web server which has been + optimized for high-performance environments. It has a + very low memory footprint compared to other web servers + and takes care of cpu-load. + - - www/thttpd: - If you are going to be serving a large amount of static content - you may find that using an application such as - thttpd is more efficient than others. - It is also optimized for excellent performance on FreeBSD. - - + + www/nginx: + nginx is a high performance + edge web server with a low memory footprint and key + features to build a modern and efficient web + infrastructure. Features include a HTTP server, HTTP + and mail reverse proxy, caching, load balancing, + compression, request throttling, connection multiplexing + and reuse, SSL offload and HTTP media streaming. + + + + www/thttpd: If you are going to + be serving a large amount of static content you may find + that using an application such as + thttpd is more efficient than + others. It is also optimized for excellent performance + on FreeBSD. + + - + + How to Mirror FreeBSD - - Ok, now you know the requirements and how to offer - the services, but not how to get it. :-) - This section explains how to actually mirror - the various parts of FreeBSD, what tools to use, - and where to mirror from. - + + Ok, now you know the requirements and how to offer the + services, but not how to get it. :-) This section explains how + to actually mirror the various parts of FreeBSD, what tools to + use, and where to mirror from. + - Mirroring the FTP site - - The FTP area is the largest amount of data that - needs to be mirrored. It includes the distribution - sets required for network installation, the - branches which are actually snapshots - of checked-out source trees, the ISO Images - to write CD-ROMs with the installation distribution, - a live file system, and a snapshot of the ports tree. All of - course for various FreeBSD versions, and various architectures. - - - The best way to mirror the FTP area is rsync. - You can install the port net/rsync and then use - rsync to sync with your upstream host. - rsync is already mentioned - in . - Since rsync access is not - required, your preferred upstream site may not allow it. - You may need to hunt around a little bit to find a site - that allows rsync access. - - - Since the number of rsync - clients will have a significant impact on the server - machine, most admins impose limitations on their - server. For a mirror, you should ask the site maintainer - you are syncing from about their policy, and maybe - an exception for your host (since you are a mirror). - - - A command line to mirror FreeBSD might look like: - &prompt.user; rsync -vaHz --delete rsync://ftp4.de.FreeBSD.org/FreeBSD/ /pub/FreeBSD/ - Consult the documentation for rsync, - which is also available at - http://rsync.samba.org/, - about the various options to be used with rsync. - If you sync the whole module (unlike subdirectories), - be aware that the module-directory (here "FreeBSD") - will not be created, so you cannot omit the target directory. - Also you might - want to set up a script framework that calls such a command - via &man.cron.8;. - + Mirroring the FTP Site + + The FTP area is the largest amount of data that needs to + be mirrored. It includes the distribution + sets required for network installation, the + branches which are actually snapshots of + checked-out source trees, the ISO Images + to write CD-ROMs with the installation distribution, a live + file system, and a snapshot of the ports tree. All of course + for various FreeBSD versions, and various + architectures. + + The best way to mirror the FTP area is + rsync. You can install the port + net/rsync and then use rsync to sync with + your upstream host. rsync is + already mentioned in . + Since rsync access is not required, + your preferred upstream site may not allow it. You may need + to hunt around a little bit to find a site that allows + rsync access. + + + Since the number of rsync + clients will have a significant impact on the server + machine, most admins impose limitations on their server. + For a mirror, you should ask the site maintainer you are + syncing from about their policy, and maybe an exception for + your host (since you are a mirror). + + + A command line to mirror FreeBSD might look like: + + &prompt.user; rsync -vaHz --delete rsync://ftp4.de.FreeBSD.org/FreeBSD/ /pub/FreeBSD/ + + Consult the documentation for + rsync, which is also available at + http://rsync.samba.org/, + about the various options to be used with rsync. If you sync + the whole module (unlike subdirectories), be aware that the + module-directory (here "FreeBSD") will not be created, so you + cannot omit the target directory. Also you might want to set + up a script framework that calls such a command via + &man.cron.8;. + - Mirroring the WWW pages - - The FreeBSD website should only be mirrored via + Mirroring the WWW Pages + + The FreeBSD website should only be mirrored via rsync. - A command line to mirror the FreeBSD web site might look like: + + A command line to mirror the FreeBSD web site might look + like: + &prompt.user; rsync -vaHz --delete rsync://bit0.us-west.freebsd.org/FreeBSD-www-data/ /usr/local/www/ - - - Mirroring Packages - Due to very high requirements of bandwidth, storage and - adminstration the &os; Project has decided not to allow public - mirrors of packages. For sites with lots of machines, it might - be advantagous to run a caching HTTP proxy for the &man.pkg.8; - process. Alternatively specific packages and their dependencies - can be fetched by running something like the following: + - &prompt.user; pkg fetch -d -o /usr/local/mirror vim + + Mirroring Packages - Once those packages have been fetched, the repository metadata must be generated by running: + Due to very high requirements of bandwidth, storage and + adminstration the &os; Project has decided not to allow public + mirrors of packages. For sites with lots of machines, it + might be advantagous to run a caching HTTP proxy for the + &man.pkg.8; process. Alternatively specific packages and + their dependencies can be fetched by running something like + the following: - &prompt.user; pkg repo /usr/local/mirror + &prompt.user; pkg fetch -d -o /usr/local/mirror vim - Once the packages have been fetched and the metadata for the - repository has been generated, serve the packages up to the - client machines via HTTP. For additional information see the - man pages for &man.pkg.8;, specifically the &man.pkg-repo.8; page. - - - - How often should I mirror? - - Every mirror should be updated at a minimum of once per day. - Certainly a script with locking to prevent multiple runs - happening at the same time will be needed to run from - &man.cron.8;. Since nearly every admin does this in their own - way, specific instructions cannot be provided. It could work - something like this: - - - - - Put the command to run your mirroring application - in a script. Use of a plain /bin/sh - script is recommended. - - - - - Add some output redirections so diagnostic - messages are logged to a file. - - - - - Test if your script works. Check the logs. - - - - - Use &man.crontab.1; to add the script to the - appropriate user's &man.crontab.5;. This should be a - different user than what your FTP daemon runs as so that - if file permissions inside your FTP area are not - world-readable those files can not be accessed by anonymous - FTP. This is used to stage releases — - making sure all of the official mirror sites have all of the - necessary release files on release day. - - - - - Here are some recommended schedules: - - FTP fileset: daily - WWW pages: daily - - + Once those packages have been fetched, the repository + metadata must be generated by running: + + &prompt.user; pkg repo /usr/local/mirror + + Once the packages have been fetched and the metadata for + the repository has been generated, serve the packages up to + the client machines via HTTP. For additional information see + the man pages for &man.pkg.8;, specifically the + &man.pkg-repo.8; page. + + + + How Often Should I Mirror? + + Every mirror should be updated at a minimum of once per + day. Certainly a script with locking to prevent multiple runs + happening at the same time will be needed to run from + &man.cron.8;. Since nearly every admin does this in their own + way, specific instructions cannot be provided. It could work + something like this: + + + + Put the command to run your mirroring application in a + script. Use of a plain /bin/sh script + is recommended. + + + + Add some output redirections so diagnostic messages + are logged to a file. + + + + Test if your script works. Check the logs. + + + + Use &man.crontab.1; to add the script to the + appropriate user's &man.crontab.5;. This should be a + different user than what your FTP daemon runs as so that + if file permissions inside your FTP area are not + world-readable those files cannot be accessed by anonymous + FTP. This is used to stage releases + — making sure all of the official mirror sites have + all of the necessary release files on release day. + + + + Here are some recommended schedules: + + + + FTP fileset: daily + + + WWW pages: daily + + + + - Where to mirror from - - This is an important issue. So this section will - spend some effort to explain the backgrounds. We will say this - several times: under no circumstances should you mirror from - ftp.FreeBSD.org. - + Where to Mirror From + + This is an important issue. So this section will spend some + effort to explain the backgrounds. We will say this several + times: under no circumstances should you mirror from ftp.FreeBSD.org. + - A few words about the organization - - Mirrors are organized by country. All - official mirrors have a DNS entry of the form - ftpN.CC.FreeBSD.org. - CC (i.e. country code) is the - top level domain (TLD) - of the country where this mirror is located. - N is a number, - telling that the host would be the Nth - mirror in that country. - (Same applies to - wwwN.CC.FreeBSD.org, etc.) - There are mirrors with no CC part. - These are the mirror sites that are very well connected and - allow a large number of concurrent users. - ftp.FreeBSD.org is actually two machines, one currently - located in Denmark and the other in the United States. - It is NOT a master site and should never be - used to mirror from. Lots of online documentation leads - interactiveusers to - ftp.FreeBSD.org so automated mirroring - systems should find a different machine to mirror from. - - - Additionally there exists a hierarchy of mirrors, which - is described in terms of tiers. - The master sites are not referred to but can be - described as Tier-0. Mirrors - that mirror from these sites can be considered - Tier-1, mirrors of Tier-1-mirrors, - are Tier-2, etc. - Official sites are encouraged to be of a low tier, - but the lower the tier the higher the requirements in - terms as described in . - Also access to low-tier-mirrors may be restricted, and - access to master sites is definitely restricted. - The tier-hierarchy is not reflected - by DNS and generally not documented anywhere except - for the master sites. However, official mirrors with low numbers - like 1-4, are usually Tier-1 - (this is just a rough hint, and there is no rule). - + A few Words About the Organization + + Mirrors are organized by country. All official mirrors + have a DNS entry of the form ftpN.CC.FreeBSD.org. + CC (i.e., country code) is the + top level domain (TLD) of the country + where this mirror is located. N is a + number, telling that the host would be the + Nth mirror in that country. (Same + applies to wwwN.CC.FreeBSD.org, etc.) + There are mirrors with no CC part. These + are the mirror sites that are very well connected and allow a + large number of concurrent users. ftp.FreeBSD.org is + actually two machines, one currently located in Denmark and + the other in the United States. It is + NOT a master site and should never be + used to mirror from. Lots of online documentation leads + interactiveusers to ftp.FreeBSD.org so + automated mirroring systems should find a different machine to + mirror from. + + Additionally there exists a hierarchy of mirrors, which is + described in terms of tiers. The master + sites are not referred to but can be described as + Tier-0. Mirrors that mirror from these + sites can be considered Tier-1, mirrors + of Tier-1-mirrors, are + Tier-2, etc. Official sites are + encouraged to be of a low tier, but the + lower the tier the higher the requirements in terms as + described in . Also + access to low-tier-mirrors may be restricted, and access to + master sites is definitely restricted. The + tier-hierarchy is not reflected by DNS + and generally not documented anywhere except for the master + sites. However, official mirrors with low numbers like 1-4, + are usually Tier-1 (this is just a rough + hint, and there is no rule). + - Ok, but where should I get the stuff now? - - Under no circumstances should you mirror from ftp.FreeBSD.org. - The short answer is: from the - site that is closest to you in Internet terms, or gives you - the fastest access. - + Ok, but Where Should I get the Stuff Now? + + Under no circumstances should you mirror from ftp.FreeBSD.org. The + short answer is: from the site that is closest to you in + Internet terms, or gives you the fastest access. + - I just want to mirror from somewhere! - - If you have no special intentions or - requirements, the statement in - applies. This means: - - - - - Check for those which provide fastest access - (number of hops, round-trip-times) - and offer the services you intend to - use (like rsync). - - - - - Contact the administrators of your chosen site stating your - request, and asking about their terms and - policies. - - - - - Set up your mirror as described above. - - - + I Just Want to Mirror from Somewhere! + + If you have no special intentions or requirements, the + statement in applies. + This means: + + + + Check for those which provide fastest access (number + of hops, round-trip-times) and offer the services you + intend to use (like + rsync). + + + + Contact the administrators of your chosen site + stating your request, and asking about their terms and + policies. + + + + Set up your mirror as described above. + + + - I am an official mirror, what is the right site for me? - *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-head@freebsd.org Mon Sep 24 14:24:34 2018 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1E95310AD90A; Mon, 24 Sep 2018 14:24:34 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C8E7782DD2; Mon, 24 Sep 2018 14:24:33 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id C34F31A905; Mon, 24 Sep 2018 14:24:33 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w8OEOXMw026520; Mon, 24 Sep 2018 14:24:33 GMT (envelope-from mat@FreeBSD.org) Received: (from mat@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w8OEOXd4026519; Mon, 24 Sep 2018 14:24:33 GMT (envelope-from mat@FreeBSD.org) Message-Id: <201809241424.w8OEOXd4026519@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: mat set sender to mat@FreeBSD.org using -f From: Mathieu Arnold Date: Mon, 24 Sep 2018 14:24:33 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52297 - head/share/pgpkeys X-SVN-Group: doc-head X-SVN-Commit-Author: mat X-SVN-Commit-Paths: head/share/pgpkeys X-SVN-Commit-Revision: 52297 X-SVN-Commit-Repository: doc 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.27 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2018 14:24:34 -0000 Author: mat Date: Mon Sep 24 14:24:33 2018 New Revision: 52297 URL: https://svnweb.freebsd.org/changeset/doc/52297 Log: Update key. Modified: head/share/pgpkeys/mat.key Modified: head/share/pgpkeys/mat.key ============================================================================== --- head/share/pgpkeys/mat.key Mon Sep 24 09:34:54 2018 (r52296) +++ head/share/pgpkeys/mat.key Mon Sep 24 14:24:33 2018 (r52297) @@ -3,14 +3,14 @@ sh addkey.sh mat 3A4516F35183CE48 ; --> -uid Mathieu Arnold -uid Mathieu Arnold -uid Mathieu Arnold -sub 4096R/A99F9AA711E3DFC9 2013-09-23 [expires: 2019-09-22] - Key fingerprint = CCE8 22F3 DFA7 F33B 765C 1B72 A99F 9AA7 11E3 DFC9 +uid Mathieu Arnold +uid Mathieu Arnold +uid Mathieu Arnold +uid Mathieu Arnold +uid Mathieu Arnold +sub rsa4096/A99F9AA711E3DFC9 2013-09-23 [E] [expires: 2020-09-19] ]]> From owner-svn-doc-head@freebsd.org Mon Sep 24 16:15:18 2018 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 894BB10B0F95; Mon, 24 Sep 2018 16:15:18 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 402CF880C7; Mon, 24 Sep 2018 16:15:18 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 36AAD1BB33; Mon, 24 Sep 2018 16:15:18 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w8OGFIGo082489; Mon, 24 Sep 2018 16:15:18 GMT (envelope-from ryusuke@FreeBSD.org) Received: (from ryusuke@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w8OGFIXT082488; Mon, 24 Sep 2018 16:15:18 GMT (envelope-from ryusuke@FreeBSD.org) Message-Id: <201809241615.w8OGFIXT082488@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: ryusuke set sender to ryusuke@FreeBSD.org using -f From: Ryusuke SUZUKI Date: Mon, 24 Sep 2018 16:15:18 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52298 - head/ja_JP.eucJP/htdocs/releases X-SVN-Group: doc-head X-SVN-Commit-Author: ryusuke X-SVN-Commit-Paths: head/ja_JP.eucJP/htdocs/releases X-SVN-Commit-Revision: 52298 X-SVN-Commit-Repository: doc 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.27 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2018 16:15:18 -0000 Author: ryusuke Date: Mon Sep 24 16:15:17 2018 New Revision: 52298 URL: https://svnweb.freebsd.org/changeset/doc/52298 Log: - Merge the following from the English version: r51914 -> r52293 head/ja_JP.eucJP/htdocs/releases/index.xml Modified: head/ja_JP.eucJP/htdocs/releases/index.xml Modified: head/ja_JP.eucJP/htdocs/releases/index.xml ============================================================================== --- head/ja_JP.eucJP/htdocs/releases/index.xml Mon Sep 24 14:24:33 2018 (r52297) +++ head/ja_JP.eucJP/htdocs/releases/index.xml Mon Sep 24 16:15:17 2018 (r52298) @@ -5,7 +5,7 @@ ]> - + @@ -82,7 +82,7 @@ リリースエンジニアリング のページをご覧ください。

-

FreeBSD-STABLE +

FreeBSD-STABLE および FreeBSD-CURRENT ブランチからの最新のスナップショットを利用できます。 From owner-svn-doc-head@freebsd.org Tue Sep 25 08:57:26 2018 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 753C510AC1E1; Tue, 25 Sep 2018 08:57:26 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2AD42895FD; Tue, 25 Sep 2018 08:57:26 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 259F3260B2; Tue, 25 Sep 2018 08:57:26 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w8P8vPjw097145; Tue, 25 Sep 2018 08:57:25 GMT (envelope-from ryusuke@FreeBSD.org) Received: (from ryusuke@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w8P8vP9e097144; Tue, 25 Sep 2018 08:57:25 GMT (envelope-from ryusuke@FreeBSD.org) Message-Id: <201809250857.w8P8vP9e097144@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: ryusuke set sender to ryusuke@FreeBSD.org using -f From: Ryusuke SUZUKI Date: Tue, 25 Sep 2018 08:57:25 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52299 - head/ja_JP.eucJP/books/handbook/x11 X-SVN-Group: doc-head X-SVN-Commit-Author: ryusuke X-SVN-Commit-Paths: head/ja_JP.eucJP/books/handbook/x11 X-SVN-Commit-Revision: 52299 X-SVN-Commit-Repository: doc 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.27 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, 25 Sep 2018 08:57:26 -0000 Author: ryusuke Date: Tue Sep 25 08:57:25 2018 New Revision: 52299 URL: https://svnweb.freebsd.org/changeset/doc/52299 Log: - Merge the following from the English version: r51980 -> r52111 head/ja_JP.eucJP/books/handbook/x11/chapter.xml Modified: head/ja_JP.eucJP/books/handbook/x11/chapter.xml Modified: head/ja_JP.eucJP/books/handbook/x11/chapter.xml ============================================================================== --- head/ja_JP.eucJP/books/handbook/x11/chapter.xml Mon Sep 24 16:15:17 2018 (r52298) +++ head/ja_JP.eucJP/books/handbook/x11/chapter.xml Tue Sep 25 08:57:25 2018 (r52299) @@ -3,7 +3,7 @@ The FreeBSD Documentation Project The FreeBSD Japanese Documentation Project - Original revision: r51980 + Original revision: r52111 $FreeBSD$ --> この場合は、実行可能な .xsession というファイルを作成してください。 - &prompt.user; echo "#!/bin/sh" > ~/.xsession -&prompt.user; echo "exec /usr/local/bin/gnome-session" >> ~/.xsession -&prompt.user; chmod +x ~/.xsession + &prompt.user; echo "exec /usr/local/bin/gnome-session" > ~/.xsession @@ -1635,9 +1633,7 @@ hald_enable="YES" この方法を使うには、以下のようにして実行可能な ~/.xsession を作成してください。 - &prompt.user; echo "#!/bin/sh" > ~/.xsession -&prompt.user; echo "exec /usr/local/bin/startkde" >> ~/.xsession -&prompt.user; chmod +x ~/.xsession + &prompt.user; echo "exec /usr/local/bin/startkde" > ~/.xsession KDE を起動した後は、 ビルトインヘルプシステムから、 @@ -1671,24 +1667,31 @@ hald_enable="YES" &prompt.root; cd /usr/ports/x11-wm/xfce4 &prompt.root; make install clean + Xfce は、 + メッセージバスに D-Bus を使います。 + これらのアプリケーションは Xfce + の依存として自動的にインストールされます。 + /etc/rc.conf において、 + システム起動時に起動するように有効にしてください。 + + dbus_enable="YES" + GNOME や KDE とは異なり、 Xfce は、 ログインマネージャを提供していません。 コマンドラインから startx を実行して Xfce を起動するには、 - 以下のように Xfce のエントリを - ~/.xinitrc に追加してください。 + 以下のコマンドを使って、 + ~/.xinitrc を作成してください。 - &prompt.user; echo "exec /usr/local/bin/startxfce4 --with-ck-launch" > ~/.xinitrc + &prompt.user; echo ". /usr/local/etc/xdg/xfce4/xinitrc" > ~/.xinitrc もう一つの方法は XDM を用いる方法です。この方法を使うには、 実行可能な .xsession を作成してください。 - &prompt.user; echo "#!/bin/sh" > ~/.xsession -&prompt.user; echo "exec /usr/local/bin/startxfce4 --with-ck-launch" >> ~/.xsession -&prompt.user; chmod +x ~/.xsession + &prompt.user; echo ". /usr/local/etc/xdg/xfce4/xinitrc" > ~/.xsession From owner-svn-doc-head@freebsd.org Tue Sep 25 17:54:03 2018 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 28CC110B7400; Tue, 25 Sep 2018 17:54:03 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D1AFA7AD94; Tue, 25 Sep 2018 17:54:02 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id CC20C3CE1; Tue, 25 Sep 2018 17:54:02 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w8PHs2E2074649; Tue, 25 Sep 2018 17:54:02 GMT (envelope-from gjb@FreeBSD.org) Received: (from gjb@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w8PHs2sC074648; Tue, 25 Sep 2018 17:54:02 GMT (envelope-from gjb@FreeBSD.org) Message-Id: <201809251754.w8PHs2sC074648@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: gjb set sender to gjb@FreeBSD.org using -f From: Glen Barber Date: Tue, 25 Sep 2018 17:54:02 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52300 - head/en_US.ISO8859-1/htdocs/releases/12.0R/hardware X-SVN-Group: doc-head X-SVN-Commit-Author: gjb X-SVN-Commit-Paths: head/en_US.ISO8859-1/htdocs/releases/12.0R/hardware X-SVN-Commit-Revision: 52300 X-SVN-Commit-Repository: doc 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.27 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, 25 Sep 2018 17:54:03 -0000 Author: gjb Date: Tue Sep 25 17:54:02 2018 New Revision: 52300 URL: https://svnweb.freebsd.org/changeset/doc/52300 Log: Move CLEANDIRS within the target conditional. Use .ORDER to attempt to catch a build race that had been lingering since reconnecting hardware.html to the build. Preemptive pointyhat in case things get worse: gjb Sponsored by: The FreeBSD Foundation Modified: head/en_US.ISO8859-1/htdocs/releases/12.0R/hardware/Makefile Modified: head/en_US.ISO8859-1/htdocs/releases/12.0R/hardware/Makefile ============================================================================== --- head/en_US.ISO8859-1/htdocs/releases/12.0R/hardware/Makefile Tue Sep 25 08:57:25 2018 (r52299) +++ head/en_US.ISO8859-1/htdocs/releases/12.0R/hardware/Makefile Tue Sep 25 17:54:02 2018 (r52300) @@ -21,8 +21,6 @@ FORMATS?= html txt INSTALL_COMPRESSED?= gz INSTALL_ONLY_COMPRESSED= -CLEANDIRS+= ${.CURDIR}/svn.* - .if ${.TARGET:M${DOC}.html} MAN4TMP!= ${MKTEMP} -d ${.CURDIR}/svn.XXXXXXXX MAN4DIR= ${MAN4TMP} @@ -35,7 +33,9 @@ hardware.parsed.xml: dev-auto.ent man4-rmsrc dev-auto.ent: man4-src-checkout ${PERL} ${MAN2HWNOTES_CMD} ${MAN2HWNOTES_FLAGS} -a ${ARCHLIST} -o ${.TARGET} ${MAN4PAGES} || (rm -f ${.TARGET}) CLEANFILES+= dev-auto.ent +CLEANDIRS+= ${.CURDIR}/svn.* +.ORDER: man4-rmsrc man4-src-checkout man4-src-checkout: mkdir -p ${MAN4TMP} ${SVN} co svn://svn.freebsd.org/base/${SRCBRANCH}/share/man/man4 \ From owner-svn-doc-head@freebsd.org Tue Sep 25 18:03:41 2018 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D50810B778C; Tue, 25 Sep 2018 18:03:41 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A99F57B442; Tue, 25 Sep 2018 18:03:40 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 9ED273E98; Tue, 25 Sep 2018 18:03:40 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w8PI3eLQ079920; Tue, 25 Sep 2018 18:03:40 GMT (envelope-from gjb@FreeBSD.org) Received: (from gjb@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w8PI3e5e079919; Tue, 25 Sep 2018 18:03:40 GMT (envelope-from gjb@FreeBSD.org) Message-Id: <201809251803.w8PI3e5e079919@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: gjb set sender to gjb@FreeBSD.org using -f From: Glen Barber Date: Tue, 25 Sep 2018 18:03:40 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52301 - head/share/xml X-SVN-Group: doc-head X-SVN-Commit-Author: gjb X-SVN-Commit-Paths: head/share/xml X-SVN-Commit-Revision: 52301 X-SVN-Commit-Repository: doc 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.27 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, 25 Sep 2018 18:03:41 -0000 Author: gjb Date: Tue Sep 25 18:03:40 2018 New Revision: 52301 URL: https://svnweb.freebsd.org/changeset/doc/52301 Log: Fix an entity typo. Sponsored by: The FreeBSD Foundation Modified: head/share/xml/authors.ent Modified: head/share/xml/authors.ent ============================================================================== --- head/share/xml/authors.ent Tue Sep 25 17:54:02 2018 (r52300) +++ head/share/xml/authors.ent Tue Sep 25 18:03:40 2018 (r52301) @@ -2605,7 +2605,7 @@ - + From owner-svn-doc-head@freebsd.org Tue Sep 25 18:06:10 2018 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 140C710B7833; Tue, 25 Sep 2018 18:06:10 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BF6187B514; Tue, 25 Sep 2018 18:06:09 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id BA6F53EA2; Tue, 25 Sep 2018 18:06:09 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w8PI69Vn080071; Tue, 25 Sep 2018 18:06:09 GMT (envelope-from gjb@FreeBSD.org) Received: (from gjb@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w8PI69S3080069; Tue, 25 Sep 2018 18:06:09 GMT (envelope-from gjb@FreeBSD.org) Message-Id: <201809251806.w8PI69S3080069@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: gjb set sender to gjb@FreeBSD.org using -f From: Glen Barber Date: Tue, 25 Sep 2018 18:06:09 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52302 - in head: en_US.ISO8859-1/htdocs share/xml X-SVN-Group: doc-head X-SVN-Commit-Author: gjb X-SVN-Commit-Paths: in head: en_US.ISO8859-1/htdocs share/xml X-SVN-Commit-Revision: 52302 X-SVN-Commit-Repository: doc 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.27 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, 25 Sep 2018 18:06:10 -0000 Author: gjb Date: Tue Sep 25 18:06:09 2018 New Revision: 52302 URL: https://svnweb.freebsd.org/changeset/doc/52302 Log: Update the doceng team roster, adding new members bcr and ryusuke. Sponsored by: The FreeBSD Foundation Modified: head/en_US.ISO8859-1/htdocs/administration.xml head/share/xml/authors.ent Modified: head/en_US.ISO8859-1/htdocs/administration.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/administration.xml Tue Sep 25 18:03:40 2018 (r52301) +++ head/en_US.ISO8859-1/htdocs/administration.xml Tue Sep 25 18:06:09 2018 (r52302) @@ -116,7 +116,9 @@

  • &a.wblock.email;
  • &a.blackend.email;
  • &a.gabor.email;
    • +
  • &a.bcr.email;
  • &a.hrs.email;
    • +
  • &a.ryusuke.email;

    • FreeBSD Port Management Team Modified: head/share/xml/authors.ent ============================================================================== --- head/share/xml/authors.ent Tue Sep 25 18:03:40 2018 (r52301) +++ head/share/xml/authors.ent Tue Sep 25 18:06:09 2018 (r52302) @@ -2608,7 +2608,7 @@ - + From owner-svn-doc-head@freebsd.org Tue Sep 25 18:49:16 2018 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2596C10B843F; Tue, 25 Sep 2018 18:49:16 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C1F537C9FB; Tue, 25 Sep 2018 18:49:15 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id B71D845B0; Tue, 25 Sep 2018 18:49:15 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w8PInF68001041; Tue, 25 Sep 2018 18:49:15 GMT (envelope-from gjb@FreeBSD.org) Received: (from gjb@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w8PInFuI001040; Tue, 25 Sep 2018 18:49:15 GMT (envelope-from gjb@FreeBSD.org) Message-Id: <201809251849.w8PInFuI001040@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: gjb set sender to gjb@FreeBSD.org using -f From: Glen Barber Date: Tue, 25 Sep 2018 18:49:15 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52303 - head/share/xml X-SVN-Group: doc-head X-SVN-Commit-Author: gjb X-SVN-Commit-Paths: head/share/xml X-SVN-Commit-Revision: 52303 X-SVN-Commit-Repository: doc 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.27 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, 25 Sep 2018 18:49:16 -0000 Author: gjb Date: Tue Sep 25 18:49:15 2018 New Revision: 52303 URL: https://svnweb.freebsd.org/changeset/doc/52303 Log: Add a comma, missed in r52302. Sponsored by: The FreeBSD Foundation Modified: head/share/xml/authors.ent Modified: head/share/xml/authors.ent ============================================================================== --- head/share/xml/authors.ent Tue Sep 25 18:06:09 2018 (r52302) +++ head/share/xml/authors.ent Tue Sep 25 18:49:15 2018 (r52303) @@ -2608,7 +2608,7 @@ - + From owner-svn-doc-head@freebsd.org Tue Sep 25 19:59:21 2018 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E0E0310B9C75; Tue, 25 Sep 2018 19:59:21 +0000 (UTC) (envelope-from erj@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 90A097F2E3; Tue, 25 Sep 2018 19:59:21 +0000 (UTC) (envelope-from erj@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 88D36512A; Tue, 25 Sep 2018 19:59:21 +0000 (UTC) (envelope-from erj@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w8PJxL3d036854; Tue, 25 Sep 2018 19:59:21 GMT (envelope-from erj@FreeBSD.org) Received: (from erj@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w8PJxLYj036853; Tue, 25 Sep 2018 19:59:21 GMT (envelope-from erj@FreeBSD.org) Message-Id: <201809251959.w8PJxLYj036853@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: erj set sender to erj@FreeBSD.org using -f From: Eric Joyner Date: Tue, 25 Sep 2018 19:59:21 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52304 - head/en_US.ISO8859-1/books/porters-handbook/versions X-SVN-Group: doc-head X-SVN-Commit-Author: erj X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/porters-handbook/versions X-SVN-Commit-Revision: 52304 X-SVN-Commit-Repository: doc 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.27 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, 25 Sep 2018 19:59:22 -0000 Author: erj (src committer) Date: Tue Sep 25 19:59:21 2018 New Revision: 52304 URL: https://svnweb.freebsd.org/changeset/doc/52304 Log: Document FreeBSD version 1102503. Added new 25/50/100/200/400G media types, along with an iflib TCP checksum fix. 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 Tue Sep 25 18:49:15 2018 (r52303) +++ head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Tue Sep 25 19:59:21 2018 (r52304) @@ -2192,6 +2192,14 @@ is spelled &, < is < and > is >. June 1, 2018 11-STABLE after releng/11.2 branched. + + + 1102503 + r338931 + September 25, 2018 + 11-STABLE after merging a TCP checksum fix to &man.iflib.4; + and adding new media types to if_media.h + From owner-svn-doc-head@freebsd.org Tue Sep 25 22:13:13 2018 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9D2521091B99; Tue, 25 Sep 2018 22:13:13 +0000 (UTC) (envelope-from lwhsu@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FABD8368B; Tue, 25 Sep 2018 22:13:13 +0000 (UTC) (envelope-from lwhsu@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4A8886861; Tue, 25 Sep 2018 22:13:13 +0000 (UTC) (envelope-from lwhsu@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w8PMDDKQ008948; Tue, 25 Sep 2018 22:13:13 GMT (envelope-from lwhsu@FreeBSD.org) Received: (from lwhsu@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w8PMDDVo008947; Tue, 25 Sep 2018 22:13:13 GMT (envelope-from lwhsu@FreeBSD.org) Message-Id: <201809252213.w8PMDDVo008947@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: lwhsu set sender to lwhsu@FreeBSD.org using -f From: Li-Wen Hsu Date: Tue, 25 Sep 2018 22:13:13 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52305 - head/en_US.ISO8859-1/books/porters-handbook/versions X-SVN-Group: doc-head X-SVN-Commit-Author: lwhsu X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/porters-handbook/versions X-SVN-Commit-Revision: 52305 X-SVN-Commit-Repository: doc 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.27 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, 25 Sep 2018 22:13:13 -0000 Author: lwhsu (src,ports committer) Date: Tue Sep 25 22:13:12 2018 New Revision: 52305 URL: https://svnweb.freebsd.org/changeset/doc/52305 Log: Fix iflib's section Approved by: bjk 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 Tue Sep 25 19:59:21 2018 (r52304) +++ head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Tue Sep 25 22:13:12 2018 (r52305) @@ -2197,7 +2197,7 @@ is spelled &, < is < and > is >. 1102503 r338931 September 25, 2018 - 11-STABLE after merging a TCP checksum fix to &man.iflib.4; + 11-STABLE after merging a TCP checksum fix to &man.iflib.9; and adding new media types to if_media.h From owner-svn-doc-head@freebsd.org Wed Sep 26 15:00:09 2018 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 97AD210AF0D3; Wed, 26 Sep 2018 15:00:09 +0000 (UTC) (envelope-from trasz@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4C7FC810D7; Wed, 26 Sep 2018 15:00:09 +0000 (UTC) (envelope-from trasz@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4349818B31; Wed, 26 Sep 2018 15:00:09 +0000 (UTC) (envelope-from trasz@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w8QF09Ok020059; Wed, 26 Sep 2018 15:00:09 GMT (envelope-from trasz@FreeBSD.org) Received: (from trasz@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w8QF08Lu020054; Wed, 26 Sep 2018 15:00:08 GMT (envelope-from trasz@FreeBSD.org) Message-Id: <201809261500.w8QF08Lu020054@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: trasz set sender to trasz@FreeBSD.org using -f From: Edward Tomasz Napierala Date: Wed, 26 Sep 2018 15:00:08 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52306 - in head/en_US.ISO8859-1/htdocs: . cgi news/status X-SVN-Group: doc-head X-SVN-Commit-Author: trasz X-SVN-Commit-Paths: in head/en_US.ISO8859-1/htdocs: . cgi news/status X-SVN-Commit-Revision: 52306 X-SVN-Commit-Repository: doc 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.27 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, 26 Sep 2018 15:00:09 -0000 Author: trasz Date: Wed Sep 26 15:00:07 2018 New Revision: 52306 URL: https://svnweb.freebsd.org/changeset/doc/52306 Log: Prepare for moving the Quarterly to Markdown. This includes removing the monthly.cgi and updating various pieces of documentation. Notably missing is the French translation. Reviewed by: bcr Approved by: bcr (mentor) Sponsored by: DARPA, AFRL Differential Revision: https://reviews.freebsd.org/D17300 Deleted: head/en_US.ISO8859-1/htdocs/cgi/monthly.cgi Modified: head/en_US.ISO8859-1/htdocs/cgi/Makefile head/en_US.ISO8859-1/htdocs/news/status/README head/en_US.ISO8859-1/htdocs/news/status/howto.xml head/en_US.ISO8859-1/htdocs/news/status/status.xml head/en_US.ISO8859-1/htdocs/robots.txt Modified: head/en_US.ISO8859-1/htdocs/cgi/Makefile ============================================================================== --- head/en_US.ISO8859-1/htdocs/cgi/Makefile Tue Sep 25 22:13:12 2018 (r52305) +++ head/en_US.ISO8859-1/htdocs/cgi/Makefile Wed Sep 26 15:00:07 2018 (r52306) @@ -18,7 +18,6 @@ CGI+= mailindex.cgi CGI+= man.cgi CGI+= mid.cgi CGI+= mirror.cgi -CGI+= monthly.cgi CGI+= ports.cgi .SUFFIXES: .C .cgi Modified: head/en_US.ISO8859-1/htdocs/news/status/README ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/README Tue Sep 25 22:13:12 2018 (r52305) +++ head/en_US.ISO8859-1/htdocs/news/status/README Wed Sep 26 15:00:07 2018 (r52306) @@ -18,9 +18,8 @@ deadline Follow up on missing reports developers@ as well. Also ping individuals which are known to have something cooking. - The xml-template is at: - https://www.freebsd.org/news/status/report-sample.xml and the generator - CGI at: https://www.freebsd.org/cgi/monthly.cgi at the time of this - writing. Make sure to keep them up to date with regard to categories + https://www.freebsd.org/news/status/report-sample.xml at the time of this + writing. Make sure to keep it up to date with regard to categories to pick from and place them prominently in the CFR - otherwise people submit plain text reports and you have to format them yourself. - Reporting howto is at: https://www.freebsd.org/news/status/howto.html. Modified: head/en_US.ISO8859-1/htdocs/news/status/howto.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/howto.xml Tue Sep 25 22:13:12 2018 (r52305) +++ head/en_US.ISO8859-1/htdocs/news/status/howto.xml Wed Sep 26 15:00:07 2018 (r52306) @@ -21,7 +21,7 @@ Chisnall, experienced in technical writing.

    Do not worry if you are not a native English speaker. The team - handling status reports, monthly@FreeBSD.org, will check + handling status reports, quarterly@FreeBSD.org, will check your entries for spelling and grammar, and fix it for you.

    Introduce Your Work

    Modified: head/en_US.ISO8859-1/htdocs/news/status/status.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/status.xml Tue Sep 25 22:13:12 2018 (r52305) +++ head/en_US.ISO8859-1/htdocs/news/status/status.xml Wed Sep 26 15:00:07 2018 (r52306) @@ -13,14 +13,13 @@ -

    Next Quarterly Status Report submissions (July – - September) due: January 14th, 2018

    +

    Next Quarterly Status Report submissions (October, 2017 – + September, 2018) due: October 31th, 2018

    -

    Use the xml - generator or download and edit the - xml-template. Submissions should be submitted by e-mail to - monthly@FreeBSD.org.

    - +

    Submit your entries as Pull Requests from your fork of + FreeBSD + Quarterly Status Reports GitHub repo or submit them via e-mail to + quarterly@FreeBSD.org.

    One of the benefits of the FreeBSD development model is a focus on Modified: head/en_US.ISO8859-1/htdocs/robots.txt ============================================================================== --- head/en_US.ISO8859-1/htdocs/robots.txt Tue Sep 25 22:13:12 2018 (r52305) +++ head/en_US.ISO8859-1/htdocs/robots.txt Wed Sep 26 15:00:07 2018 (r52306) @@ -11,7 +11,6 @@ Disallow: /cgi/mailindex.cgi Disallow: /cgi/mid.cgi Disallow: /cgi/mirror.cgi Disallow: /cgi/missing_handler.cgi -Disallow: /cgi/monthly.cgi Disallow: /cgi/ports.cgi Disallow: /cgi/query-pr-summary.cgi Disallow: /cgi/query-pr.cgi From owner-svn-doc-head@freebsd.org Wed Sep 26 16:03:12 2018 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8D93F10B08E1; Wed, 26 Sep 2018 16:03:12 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3C02D837C6; Wed, 26 Sep 2018 16:03:12 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 3595A196BE; Wed, 26 Sep 2018 16:03:12 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w8QG3CHN058131; Wed, 26 Sep 2018 16:03:12 GMT (envelope-from ryusuke@FreeBSD.org) Received: (from ryusuke@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w8QG3CtJ058130; Wed, 26 Sep 2018 16:03:12 GMT (envelope-from ryusuke@FreeBSD.org) Message-Id: <201809261603.w8QG3CtJ058130@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: ryusuke set sender to ryusuke@FreeBSD.org using -f From: Ryusuke SUZUKI Date: Wed, 26 Sep 2018 16:03:12 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52307 - head/en_US.ISO8859-1/htdocs/java X-SVN-Group: doc-head X-SVN-Commit-Author: ryusuke X-SVN-Commit-Paths: head/en_US.ISO8859-1/htdocs/java X-SVN-Commit-Revision: 52307 X-SVN-Commit-Repository: doc 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.27 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, 26 Sep 2018 16:03:12 -0000 Author: ryusuke Date: Wed Sep 26 16:03:11 2018 New Revision: 52307 URL: https://svnweb.freebsd.org/changeset/doc/52307 Log: Use HTTPS for FreshPorts Modified: head/en_US.ISO8859-1/htdocs/java/index.xml Modified: head/en_US.ISO8859-1/htdocs/java/index.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/java/index.xml Wed Sep 26 15:00:07 2018 (r52306) +++ head/en_US.ISO8859-1/htdocs/java/index.xml Wed Sep 26 16:03:11 2018 (r52307) @@ -50,7 +50,7 @@

    &openjdk; 8 is frequently updated, and it is suggested to refer to a revision log for detailed release history. Additionally, one may choose to review more information at - FreshPorts.

    + FreshPorts.

    To install &openjdk; 8 package use the pkg(8) utility:

    From owner-svn-doc-head@freebsd.org Thu Sep 27 10:06:38 2018 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B4DD10A96F6; Thu, 27 Sep 2018 10:06:38 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BC7FE7EA17; Thu, 27 Sep 2018 10:06:37 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id B75E424928; Thu, 27 Sep 2018 10:06:37 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w8RA6b7d013660; Thu, 27 Sep 2018 10:06:37 GMT (envelope-from ryusuke@FreeBSD.org) Received: (from ryusuke@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w8RA6b7V013659; Thu, 27 Sep 2018 10:06:37 GMT (envelope-from ryusuke@FreeBSD.org) Message-Id: <201809271006.w8RA6b7V013659@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: ryusuke set sender to ryusuke@FreeBSD.org using -f From: Ryusuke SUZUKI Date: Thu, 27 Sep 2018 10:06:37 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52308 - head/ja_JP.eucJP/htdocs/java X-SVN-Group: doc-head X-SVN-Commit-Author: ryusuke X-SVN-Commit-Paths: head/ja_JP.eucJP/htdocs/java X-SVN-Commit-Revision: 52308 X-SVN-Commit-Repository: doc 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.27 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, 27 Sep 2018 10:06:38 -0000 Author: ryusuke Date: Thu Sep 27 10:06:37 2018 New Revision: 52308 URL: https://svnweb.freebsd.org/changeset/doc/52308 Log: - Merge the following from the English version: r52174 -> r52307 head/ja_JP.eucJP/htdocs/java/index.xml Modified: head/ja_JP.eucJP/htdocs/java/index.xml Modified: head/ja_JP.eucJP/htdocs/java/index.xml ============================================================================== --- head/ja_JP.eucJP/htdocs/java/index.xml Wed Sep 26 16:03:11 2018 (r52307) +++ head/ja_JP.eucJP/htdocs/java/index.xml Thu Sep 27 10:06:37 2018 (r52308) @@ -5,7 +5,7 @@ - + ]> @@ -58,7 +58,7 @@ 詳細なリリースの変遷を知るには、 リビジョンログ を参照してください。さらに、 - FreshPorts + FreshPorts でより多くの情報をレビューすることもできます。

    &openjdk; 8 package をインストールするには、 From owner-svn-doc-head@freebsd.org Thu Sep 27 10:39:47 2018 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B057210AA38C; Thu, 27 Sep 2018 10:39:47 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 540837FDB6; Thu, 27 Sep 2018 10:39:47 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 493C424E67; Thu, 27 Sep 2018 10:39:47 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w8RAdlMY028868; Thu, 27 Sep 2018 10:39:47 GMT (envelope-from ryusuke@FreeBSD.org) Received: (from ryusuke@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w8RAdlUt028867; Thu, 27 Sep 2018 10:39:47 GMT (envelope-from ryusuke@FreeBSD.org) Message-Id: <201809271039.w8RAdlUt028867@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: ryusuke set sender to ryusuke@FreeBSD.org using -f From: Ryusuke SUZUKI Date: Thu, 27 Sep 2018 10:39:47 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52309 - head/ja_JP.eucJP/htdocs/projects/mips X-SVN-Group: doc-head X-SVN-Commit-Author: ryusuke X-SVN-Commit-Paths: head/ja_JP.eucJP/htdocs/projects/mips X-SVN-Commit-Revision: 52309 X-SVN-Commit-Repository: doc 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.27 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, 27 Sep 2018 10:39:47 -0000 Author: ryusuke Date: Thu Sep 27 10:39:46 2018 New Revision: 52309 URL: https://svnweb.freebsd.org/changeset/doc/52309 Log: - Merge the following from the English version: r37602 -> r51348 head/ja_JP.eucJP/htdocs/projects/mips/index.xml Modified: head/ja_JP.eucJP/htdocs/projects/mips/index.xml Modified: head/ja_JP.eucJP/htdocs/projects/mips/index.xml ============================================================================== --- head/ja_JP.eucJP/htdocs/projects/mips/index.xml Thu Sep 27 10:06:37 2018 (r52308) +++ head/ja_JP.eucJP/htdocs/projects/mips/index.xml Thu Sep 27 10:39:46 2018 (r52309) @@ -5,10 +5,13 @@ - + + + + "> @@ -30,6 +33,7 @@ +

    プロジェクトの目的

    FreeBSD/MIPS プロジェクトは、 @@ -59,7 +63,7 @@

    • FreeBSD.org wiki の FreeBSD/MIPS port + href="https://wiki.freebsd.org/FreeBSD/mips">FreeBSD/MIPS port ページ。このページには、FreeBSD/mips の構築に関する情報が含まれています。

    • MIPS 全般についての情報は、 MIPS Technologies, Inc. From owner-svn-doc-head@freebsd.org Thu Sep 27 12:46:58 2018 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5547110ADBDD; Thu, 27 Sep 2018 12:46:58 +0000 (UTC) (envelope-from 0mp@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F1DA8840E0; Thu, 27 Sep 2018 12:46:57 +0000 (UTC) (envelope-from 0mp@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id E7B7A263DC; Thu, 27 Sep 2018 12:46:57 +0000 (UTC) (envelope-from 0mp@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w8RCkvVZ094657; Thu, 27 Sep 2018 12:46:57 GMT (envelope-from 0mp@FreeBSD.org) Received: (from 0mp@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w8RCkvDX094656; Thu, 27 Sep 2018 12:46:57 GMT (envelope-from 0mp@FreeBSD.org) Message-Id: <201809271246.w8RCkvDX094656@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: 0mp set sender to 0mp@FreeBSD.org using -f From: Mateusz Piotrowski <0mp@FreeBSD.org> Date: Thu, 27 Sep 2018 12:46:57 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52310 - head/en_US.ISO8859-1/htdocs/snapshots X-SVN-Group: doc-head X-SVN-Commit-Author: 0mp X-SVN-Commit-Paths: head/en_US.ISO8859-1/htdocs/snapshots X-SVN-Commit-Revision: 52310 X-SVN-Commit-Repository: doc 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.27 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, 27 Sep 2018 12:46:58 -0000 Author: 0mp (ports committer) Date: Thu Sep 27 12:46:57 2018 New Revision: 52310 URL: https://svnweb.freebsd.org/changeset/doc/52310 Log: Fix a typo on the FreeBSD Snapshot Releases website. We mention 11-STABLE twice instead of mentioning 10-STABLE. Reviewed by: mat Approved by: mat (mentor) Sponsored by: Bally Wulff Games & Entertainment GmbH Differential Revision: https://reviews.freebsd.org/D17312 Modified: head/en_US.ISO8859-1/htdocs/snapshots/index.xml Modified: head/en_US.ISO8859-1/htdocs/snapshots/index.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/snapshots/index.xml Thu Sep 27 10:39:46 2018 (r52309) +++ head/en_US.ISO8859-1/htdocs/snapshots/index.xml Thu Sep 27 12:46:57 2018 (r52310) @@ -42,7 +42,7 @@ &rel.head.major;-CURRENT, &rel.current.major;-STABLE and - &rel1.current.major;-STABLE + &rel2.current.major;-STABLE are available in directories whose URLs have the format &url.snapshots;<target>/<target_arch>/ where <target> and <target_arch> From owner-svn-doc-head@freebsd.org Thu Sep 27 16:33:39 2018 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A81E010B2B92; Thu, 27 Sep 2018 16:33:39 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5DA678C758; Thu, 27 Sep 2018 16:33:39 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 587689E4; Thu, 27 Sep 2018 16:33:39 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w8RGXdr2012278; Thu, 27 Sep 2018 16:33:39 GMT (envelope-from gjb@FreeBSD.org) Received: (from gjb@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w8RGXdiA012277; Thu, 27 Sep 2018 16:33:39 GMT (envelope-from gjb@FreeBSD.org) Message-Id: <201809271633.w8RGXdiA012277@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: gjb set sender to gjb@FreeBSD.org using -f From: Glen Barber Date: Thu, 27 Sep 2018 16:33:39 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52311 - head/en_US.ISO8859-1/htdocs/releases/12.0R X-SVN-Group: doc-head X-SVN-Commit-Author: gjb X-SVN-Commit-Paths: head/en_US.ISO8859-1/htdocs/releases/12.0R X-SVN-Commit-Revision: 52311 X-SVN-Commit-Repository: doc 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.27 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, 27 Sep 2018 16:33:39 -0000 Author: gjb Date: Thu Sep 27 16:33:38 2018 New Revision: 52311 URL: https://svnweb.freebsd.org/changeset/doc/52311 Log: Update the 12.0-RELEASE schedule to account for another slip in branching stable/12. Approved by: re (implicit) Sponsored by: The FreeBSD Foundation Modified: head/en_US.ISO8859-1/htdocs/releases/12.0R/schedule.xml Modified: head/en_US.ISO8859-1/htdocs/releases/12.0R/schedule.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/releases/12.0R/schedule.xml Thu Sep 27 12:46:57 2018 (r52310) +++ head/en_US.ISO8859-1/htdocs/releases/12.0R/schedule.xml Thu Sep 27 16:33:38 2018 (r52311) @@ -108,7 +108,7 @@ &local.branch.stable; branch - 28 September 2018 + 12 October 2018 - Subversion branch created; release engineering continues on this branch. @@ -116,14 +116,14 @@ BETA1 builds begin - 28 September 2018 + 12 October 2018 - First beta test snapshot. &local.branch.head; thaw - 30 September 2018 + 14 October 2018 - The code freeze on the &local.branch.head; branch is lifted. @@ -131,21 +131,21 @@ BETA2 builds begin - 5 October 2018 + 19 October 2018 - Second beta test snapshot. BETA3 builds begin * - 12 October 2018 + 26 October 2018 - Third beta test snapshot. &local.branch.releng; branch - 19 October 2018 + 2 November 2018 - Subversion branch created; future release engineering proceeds on this branch. @@ -153,14 +153,14 @@ RC1 builds begin - 19 October 2018 + 2 November 2018 - First release candidate. &local.branch.stable; thaw - 21 October 2018 + 4 November 2018 - The code freeze on the &local.branch.stable; branch is lifted. @@ -168,28 +168,28 @@ RC2 builds begin - 26 October 2018 + 9 November 2018 - Second release candidate. RC3 builds begin * - 2 November 2018 + 16 November 2018 - Third release candidate. RELEASE builds begin - 9 November 2018 + 23 November 2018 - &local.rel;-RELEASE builds begin. RELEASE announcement - 13 November 2018 + 27 November 2018 - &local.rel;-RELEASE press release. From owner-svn-doc-head@freebsd.org Thu Sep 27 19:11:51 2018 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B7E6610B672C; Thu, 27 Sep 2018 19:11:50 +0000 (UTC) (envelope-from gordon@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6CC8372A70; Thu, 27 Sep 2018 19:11:50 +0000 (UTC) (envelope-from gordon@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 678EA23CE; Thu, 27 Sep 2018 19:11:50 +0000 (UTC) (envelope-from gordon@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w8RJBoFc094332; Thu, 27 Sep 2018 19:11:50 GMT (envelope-from gordon@FreeBSD.org) Received: (from gordon@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w8RJBmpb094317; Thu, 27 Sep 2018 19:11:48 GMT (envelope-from gordon@FreeBSD.org) Message-Id: <201809271911.w8RJBmpb094317@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: gordon set sender to gordon@FreeBSD.org using -f From: Gordon Tetlow Date: Thu, 27 Sep 2018 19:11:48 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52312 - in head/share: security/advisories security/patches/EN-18:09 security/patches/EN-18:10 security/patches/EN-18:11 security/patches/EN-18:12 xml X-SVN-Group: doc-head X-SVN-Commit-Author: gordon X-SVN-Commit-Paths: in head/share: security/advisories security/patches/EN-18:09 security/patches/EN-18:10 security/patches/EN-18:11 security/patches/EN-18:12 xml X-SVN-Commit-Revision: 52312 X-SVN-Commit-Repository: doc 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.27 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, 27 Sep 2018 19:11:51 -0000 Author: gordon (src,ports committer) Date: Thu Sep 27 19:11:47 2018 New Revision: 52312 URL: https://svnweb.freebsd.org/changeset/doc/52312 Log: Add errata notices EN-18:09 through EN-18:12 Approved by: so Added: head/share/security/advisories/FreeBSD-EN-18:09.ip.asc (contents, props changed) head/share/security/advisories/FreeBSD-EN-18:10.syscall.asc (contents, props changed) head/share/security/advisories/FreeBSD-EN-18:11.listen.asc (contents, props changed) head/share/security/advisories/FreeBSD-EN-18:12.mem.asc (contents, props changed) head/share/security/patches/EN-18:09/ head/share/security/patches/EN-18:09/ip.patch (contents, props changed) head/share/security/patches/EN-18:09/ip.patch.asc (contents, props changed) head/share/security/patches/EN-18:10/ head/share/security/patches/EN-18:10/syscall-11.patch (contents, props changed) head/share/security/patches/EN-18:10/syscall-11.patch.asc (contents, props changed) head/share/security/patches/EN-18:11/ head/share/security/patches/EN-18:11/listen-10.patch (contents, props changed) head/share/security/patches/EN-18:11/listen-10.patch.asc (contents, props changed) head/share/security/patches/EN-18:11/listen-11.patch (contents, props changed) head/share/security/patches/EN-18:11/listen-11.patch.asc (contents, props changed) head/share/security/patches/EN-18:12/ head/share/security/patches/EN-18:12/mem.patch (contents, props changed) head/share/security/patches/EN-18:12/mem.patch.asc (contents, props changed) Modified: head/share/xml/notices.xml Added: head/share/security/advisories/FreeBSD-EN-18:09.ip.asc ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/share/security/advisories/FreeBSD-EN-18:09.ip.asc Thu Sep 27 19:11:47 2018 (r52312) @@ -0,0 +1,136 @@ +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA512 + +============================================================================= +FreeBSD-EN-18:09.ip Errata Notice + The FreeBSD Project + +Topic: IP fragment remediation causes IPv6 fragment + reassembly failure + +Category: core +Module: kernel +Announced: 2018-09-27 +Credits: Kristof Provost +Affects: FreeBSD 11.1 and FreeBSD 11.2 +Corrected: 2018-09-27 18:29:55 UTC (releng/11.2, 11.2-RELEASE-p4) + 2018-09-27 18:29:55 UTC (releng/11.1, 11.1-RELEASE-p15) + +For general information regarding FreeBSD Errata Notices and Security +Advisories, including descriptions of the fields above, security +branches, and the following sections, please visit +. + +I. Background + +The recent security advisory titled SA-18:10.ip resolved an issue in the IPv4 +and IPv6 fragment reassembly code. + +II. Problem Description + +As a result of fixing the issue describe in SA-18:10.ip, a regression was +introduced in the IPv6 fragment hashing code which could cause reassembly to +fail. + +III. Impact + +Received IPv6 packets requiring fragment reassembly may be dropped instead of +properly reassembled and delivered. + +IV. Workaround + +Disable IPv6 fragment reassembly, using these commands: + % sysctl net.inet6.ip6.maxfrags=0 + +On systems compiled with VIMAGE, these sysctls will need to be +executed for each VNET. + +V. Solution + +Perform one of the following: + +1) Upgrade your system to a supported FreeBSD stable or release / security +branch (releng) dated after the correction date. + +Afterward, reboot the system. + +2) To update your system via a binary patch: + +Systems running a RELEASE version of FreeBSD on the i386 or amd64 +platforms can be updated via the freebsd-update(8) utility: + +# freebsd-update fetch +# freebsd-update install + +Afterward, reboot the system. + +3) To update your system via a source code patch: + +The following patches have been verified to apply to the applicable +FreeBSD release branches. + +a) Download the relevant patch from the location below, and verify the +detached PGP signature using your PGP utility. + +[FreeBSD 11.x] +# fetch https://security.FreeBSD.org/patches/EN-18:09/ip.patch +# fetch https://security.FreeBSD.org/patches/EN-18:09/ip.patch.asc +# gpg --verify ip.patch.asc + +b) Apply the patch. Execute the following commands as root: + +# cd /usr/src +# patch < /path/to/patch + +c) Recompile your kernel as described in + and reboot the +system. + +VI. Correction details + +The following list contains the correction revision numbers for each +affected branch. + +Branch/path Revision +- ------------------------------------------------------------------------- +releng/11.1/ r338978 +releng/11.2/ r338978 +- ------------------------------------------------------------------------- + +To see which files were modified by a particular revision, run the +following command, replacing NNNNNN with the revision number, on a +machine with Subversion installed: + +# svn diff -cNNNNNN --summarize svn://svn.freebsd.org/base + +Or visit the following URL, replacing NNNNNN with the revision number: + + + +VII. References + +The security advisory that introduced the regression is available at + + + + +The latest revision of this advisory is available at + +-----BEGIN PGP SIGNATURE----- + +iQKTBAEBCgB9FiEE/A6HiuWv54gCjWNV05eS9J6n5cIFAlutKTVfFIAAAAAALgAo +aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEZD +MEU4NzhBRTVBRkU3ODgwMjhENjM1NUQzOTc5MkY0OUVBN0U1QzIACgkQ05eS9J6n +5cKagRAAh4AnkPqG5hNnpilNct2cjY6GrU+Ex0hmbDbv36RR5Cj/Xi6FrdjGdF6/ +sA5/KYC1fOe07S2JJDgh2b5f1E3NBtfCCXQL3Fq46LRu8KJUifReY23kxNw74pev +86WmxtctkJ62gc3EUhaTx5tgvIqHRnLrNbJqAJ9VEZkV5aa33yT/5zDTq0TLJPsK +LfgwIWw7KAecH28cHx9KH+QyeLEsKoQPj5PIpQih7aZE/8cVLIMxKepExzPFx0s8 +SV1BFVQqJaRK4frv7tHZIEjTrseKVhF6SCqbtSVP6ZBtOAaaNGobq9bQNzPPxls7 +tTIGC6JVacUNNzJY+uv+DyHwCcEqyU5HQKOaJGqcQ4rxccXdWLBQOA55sRuiCZSy +SxRzs+4JNo2XDACnSECUFFos05HXxOWm8lqt8juR6fnq9Auej/PmktQYHaIXI3us +hYOlHu7Oo6sSGERBE92I1B4Y0L2BzXgroFN+rKmzlLGmM3vQYDxt2o0/GpMRf0wf +I+plRLC9osYTc/QFJzqt6dGJj+46xWyCw8aGcRhtQGPWUcB3DtYRjJxi1x6YjBkN +Cw3nepcW4rwJpmJZyGuNhsyKFZlhhz2+GV1lxsoe5TC6rRbEo30O3aU1zh5+fljo +KR9WSfy6bNoTX4NhbCJ+j9fdD6AxiqWtmB8h4Vp7ykrM/VJLUzc= +=1FtK +-----END PGP SIGNATURE----- Added: head/share/security/advisories/FreeBSD-EN-18:10.syscall.asc ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/share/security/advisories/FreeBSD-EN-18:10.syscall.asc Thu Sep 27 19:11:47 2018 (r52312) @@ -0,0 +1,132 @@ +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA512 + +============================================================================= +FreeBSD-EN-18:10.syscall Errata Notice + The FreeBSD Project + +Topic: NULL pointer dereference in freebsd4_getfsstat system call + +Category: core +Module: kernel +Announced: 2018-09-27 +Credits: Thomas Barabosch, Fraunhofer FKIE +Affects: FreeBSD 11.x +Corrected: 2018-09-27 18:54:41 UTC (stable/11, 11.1-STABLE) + 2018-09-27 18:32:14 UTC (releng/11.2, 11.2-RELEASE-p4) + 2018-09-27 18:32:14 UTC (releng/11.1, 11.1-RELEASE-p15) +CVE Name: CVE-2018-17154 + +For general information regarding FreeBSD Errata Notices and Security +Advisories, including descriptions of the fields above, security +branches, and the following sections, please visit +. + +I. Background + +The freebsd4_getfsstat system call returns information about all mounted file +systems in a binary format compatible with FreeBSD 4.x. Part of the call +includes passing in a userland allocated buffer for the system call to fill +along with the size of the buffer. + +II. Problem Description + +Insufficient checking occurs on the buffer when a very large buffer size causes +memory allocation to fail. Resulting code attempts to free the NULL pointer. + +III. Impact + +A local unprivileged user may cause a denial of service using a specially +crafted binary. + +IV. Workaround + +No workaround is available. + +V. Solution + +Perform one of the following: + +1) Upgrade your system to a supported FreeBSD stable or release / security +branch (releng) dated after the correction date. + +Afterward, reboot the system. + +2) To update your system via a binary patch: + +Systems running a RELEASE version of FreeBSD on the i386 or amd64 +platforms can be updated via the freebsd-update(8) utility: + +# freebsd-update fetch +# freebsd-update install + +Afterward, reboot the system. + +3) To update your system via a source code patch: + +The following patches have been verified to apply to the applicable +FreeBSD release branches. + +a) Download the relevant patch from the location below, and verify the +detached PGP signature using your PGP utility. + +[FreeBSD 11.x] +# fetch https://security.FreeBSD.org/patches/EN-18:10/syscall-11.patch +# fetch https://security.FreeBSD.org/patches/EN-18:10/syscall-11.patch.asc +# gpg --verify syscall-11.patch.asc + +b) Apply the patch. Execute the following commands as root: + +# cd /usr/src +# patch < /path/to/patch + +c) Recompile your kernel as described in + and reboot the +system. + +VI. Correction details + +The following list contains the correction revision numbers for each +affected branch. + +Branch/path Revision +- ------------------------------------------------------------------------- +stable/11/ r338987 +releng/11.1/ r338979 +releng/11.2/ r338979 +- ------------------------------------------------------------------------- + +To see which files were modified by a particular revision, run the +following command, replacing NNNNNN with the revision number, on a +machine with Subversion installed: + +# svn diff -cNNNNNN --summarize svn://svn.freebsd.org/base + +Or visit the following URL, replacing NNNNNN with the revision number: + + + +VII. References + + + +The latest revision of this advisory is available at + +-----BEGIN PGP SIGNATURE----- + +iQKSBAEBCgB9FiEE/A6HiuWv54gCjWNV05eS9J6n5cIFAlutKT9fFIAAAAAALgAo +aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEZD +MEU4NzhBRTVBRkU3ODgwMjhENjM1NUQzOTc5MkY0OUVBN0U1QzIACgkQ05eS9J6n +5cJMqQ/4ycdylBNCX0cqFDYrtDU0OJO0mEi2LKqCM31YzOCLbKLtVSq06rxOj/E9 +0okWag0NxaGIo2+7+b/hykDwL+1Rwpa5YNdODESRYQeW0OVdnmy/JSB/8q2I2BwX +PrqMc38sc9YuCz202B7tj4CQRKyhe2/qWRXANzh4jolC8zIuP7zAH6bMO+jc4XJS +9qe2YdvChWiwLJXOSXaqZf1xY1jY08+lRGDx03n13OLRN8PZdbIoDEmOd2/vxhcV +YRcDH0axLJSyngknPE9gU8iVZDunxpNBool5hJYDd8rBbAfypXWSDZ7wJGUn7tUZ +3Cj/NPmZ9auMTGLgpRJB/bhgCnn3mZQ5QjR1egonZf3uIlTWZ+0C9GhJjh5cw+2p +3hF+202uJicNm5TSkO6QpavVVvQNFcuCR54ZvXEICv3YNam3yDupGWsbjHloxoCw +7A/wmBBcbtAJ7ujzgPm4+yN5Vno4dcPmkIfW9bz0fwXzYF1VEaF5pZZu7a9bjdI0 +xHBk2v77NIRBxC5i1KK5R5Guj0UY0EvkclBTF4Twh3TP0SAPN+5sqpmBRQwPGEdp +9v5TPQv5DJn0KTJwkdrrP+70WIYkfcUVJ9hJYbXAMXseN1q3mTggS/ypF9ckTP0Z +D1hQuUySz07GInHlJ+znS8CzVSj/iWqsxThBBbwgy1a4haxr5A== +=HCqG +-----END PGP SIGNATURE----- Added: head/share/security/advisories/FreeBSD-EN-18:11.listen.asc ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/share/security/advisories/FreeBSD-EN-18:11.listen.asc Thu Sep 27 19:11:47 2018 (r52312) @@ -0,0 +1,146 @@ +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA512 + +============================================================================= +FreeBSD-EN-18:11.listen Errata Notice + The FreeBSD Project + +Topic: Denial of service in listen syscall over IPv6 socket + +Category: core +Module: kernel +Announced: 2018-09-27 +Credits: Jakub Jirasek, Secunia Research at Flexera +Affects: All supported versions of FreeBSD. +Corrected: 2018-09-27 18:50:10 UTC (stable/11, 11.2-STABLE) + 2018-09-27 18:34:42 UTC (releng/11.2, 11.2-RELEASE-p4) + 2018-09-27 18:34:42 UTC (releng/11.1, 11.1-RELEASE-p15) + 2018-09-27 18:48:50 UTC (stable/10, 10.4-STABLE) + 2018-09-27 18:34:42 UTC (releng/10.4, 10.4-RELEASE-p13) +CVE Name: CVE-2018-6925 + +For general information regarding FreeBSD Errata Notices and Security +Advisories, including descriptions of the fields above, security +branches, and the following sections, please visit +. + +I. Background + +The protocol control block is a structure that maintains the network layer +state for various sockets. There are various state flags that must be +properly maintained to keep the structure consistent. + +II. Problem Description + +There are various cases in the IPv6 socket code where the protocol control +block's state flags are modified during a syscall, but are not restored if +the operation fails. This can leave the control block in an inconsistent +state. + +III. Impact + +A local unprivileged user could exploit the inconsistent state of the +protocol control block to cause the kernel to crash, leading to a denial of +service. + +IV. Workaround + +No workaround is available. + +V. Solution + +Perform one of the following: + +1) Upgrade your system to a supported FreeBSD stable or release / security +branch (releng) dated after the correction date. + +Afterward, reboot the system. + +2) To update your system via a binary patch: + +Systems running a RELEASE version of FreeBSD on the i386 or amd64 +platforms can be updated via the freebsd-update(8) utility: + +# freebsd-update fetch +# freebsd-update install + +Afterward, reboot the system. + +3) To update your system via a source code patch: + +The following patches have been verified to apply to the applicable +FreeBSD release branches. + +a) Download the relevant patch from the location below, and verify the +detached PGP signature using your PGP utility. + +[FreeBSD 11.x] +# fetch https://security.FreeBSD.org/patches/EN-18:11/listen-11.patch +# fetch https://security.FreeBSD.org/patches/EN-18:11/listen-11.patch.asc +# gpg --verify listen-11.patch.asc + +[FreeBSD 10.4] +# fetch https://security.FreeBSD.org/patches/EN-18:11/listen-10.patch +# fetch https://security.FreeBSD.org/patches/EN-18:11/listen-10.patch.asc +# gpg --verify listen-10.patch.asc + +b) Apply the patch. Execute the following commands as root: + +# cd /usr/src +# patch < /path/to/patch + +c) Recompile your kernel as described in + and reboot the +system. + +VI. Correction details + +The following list contains the correction revision numbers for each +affected branch. + +Branch/path Revision +- ------------------------------------------------------------------------- +stable/10/ r338985 +releng/10.4/ r338980 +stable/11/ r338986 +releng/11.1/ r338980 +releng/11.2/ r338980 +- ------------------------------------------------------------------------- + +To see which files were modified by a particular revision, run the +following command, replacing NNNNNN with the revision number, on a +machine with Subversion installed: + +# svn diff -cNNNNNN --summarize svn://svn.freebsd.org/base + +Or visit the following URL, replacing NNNNNN with the revision number: + + + +VII. References + + + +For information about Secunia Research: + + +The latest revision of this advisory is available at + +-----BEGIN PGP SIGNATURE----- + +iQKTBAEBCgB9FiEE/A6HiuWv54gCjWNV05eS9J6n5cIFAlutKURfFIAAAAAALgAo +aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEZD +MEU4NzhBRTVBRkU3ODgwMjhENjM1NUQzOTc5MkY0OUVBN0U1QzIACgkQ05eS9J6n +5cIUEA/+JxBo76dRre8nfvYcN2PJGGFn8i2mWwSG87SWwQUeKlkgpJCV8qMnVEr2 +dGz3gwBsxFLKUjQVyl+IwFkaJgKXMbFYkfIqLaS+3a12KLllFAn2Q0dnN+oxFhS2 +Wpx4DkDRgBzEyLokxwjUCtg2fd6HPlML2YXCR5SqjXDOoBGAR9GCCXXYNnWSC00y +IYgeC8UpE3ykTlwDH8q+LgLqtnx/oDW1h6UR12alP0ytH8+BldiAqRxjHE3/Wv2E +aU8m8YuAAIW4tHZ4vdqpiFP4grN/0tSf/DEPBTtVIv5FGpXSk61YTBSm4OMIKNN8 +QEVEA6n6NEGSKYrbB5BE73KYgCAaeGzcGikX9F4aAlN5GSPBVJ66SEbk16YDzDfB +KimjhityEP5YXh8hVkNo6fq+17dKpqx81390wzcXeDlBTIkANnKLh23gE0RuniNY +dXrPE2HWSpkCnWN6l0BImefDeCgAaF7KZK+z7bbsn2D7UMGFGeHU/XlRM0ze7OOV +ETqwk2M4GuxddHTKktNGBItWVd6EjReAh6QOo1kAA4qMKuNIiDQdRS72x6fUbmlA +ZIOzPNd6TS57aKSnAZlR1SpvRMqo+g9cetMxuJmKnQ+hXaRk2zJVuP2RAJuoFFqf +TmnVAPpDRjoYa0lf2YkOKtYcfF+pBcWI1CVAEFuQG2PheJRYns0= +=jMY6 +-----END PGP SIGNATURE----- Added: head/share/security/advisories/FreeBSD-EN-18:12.mem.asc ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/share/security/advisories/FreeBSD-EN-18:12.mem.asc Thu Sep 27 19:11:47 2018 (r52312) @@ -0,0 +1,139 @@ +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA512 + +============================================================================= +FreeBSD-EN-18:12.mem Errata Notice + The FreeBSD Project + +Topic: Small kernel memory disclosures in two system calls + +Category: core +Module: kernel +Announced: 2018-09-27 +Credits: Thomas Barabosch, Fraunhofer FKIE +Affects: All supported versions of FreeBSD. +Corrected: 2018-09-27 18:42:40 UTC (stable/11, 11.2-STABLE) + 2018-09-27 18:36:30 UTC (releng/11.2, 11.2-RELEASE-p4) + 2018-09-27 18:36:30 UTC (releng/11.1, 11.1-RELEASE-p15) + 2018-09-27 18:44:40 UTC (stable/10, 10.4-STABLE) + 2018-09-27 18:36:30 UTC (releng/10.4, 10.4-RELEASE-p13) +CVE Name: CVE-2018-17155 + +For general information regarding FreeBSD Errata Notices and Security +Advisories, including descriptions of the fields above, security +branches, and the following sections, please visit +. + +I. Background + +The kernel provides an interface for userland programs via system calls. Two +of these system calls are named getcontext and swapcontext. + +II. Problem Description + +Due to insufficient initialization of memory copied to userland in the +getcontext and swapcontext system calls, small amounts of kernel memory may +be disclosed to userland processes. + +III. Impact + +An unprivileged local user may be able to create a specific program to read +the contents of small portions of kernel memory. + +Such memory might contain sensitive information, such as portions of the file +cache or terminal buffers. This information might be directly useful, or it +might be leveraged to obtain elevated privileges in some way; for example, +a terminal buffer might include a user-entered password. + +IV. Workaround + +No workaround is available. + +V. Solution + +Perform one of the following: + +1) Upgrade your system to a supported FreeBSD stable or release / security +branch (releng) dated after the correction date. + +Afterward, reboot the system. + +2) To update your system via a binary patch: + +Systems running a RELEASE version of FreeBSD on the i386 or amd64 +platforms can be updated via the freebsd-update(8) utility: + +# freebsd-update fetch +# freebsd-update install + +Afterward, reboot the system. + +3) To update your system via a source code patch: + +The following patches have been verified to apply to the applicable +FreeBSD release branches. + +a) Download the relevant patch from the location below, and verify the +detached PGP signature using your PGP utility. + +# fetch https://security.FreeBSD.org/patches/EN-18:12/mem.patch +# fetch https://security.FreeBSD.org/patches/EN-18:12/mem.patch.asc +# gpg --verify mem.patch.asc + +b) Apply the patch. Execute the following commands as root: + +# cd /usr/src +# patch < /path/to/patch + +c) Recompile your kernel as described in + and reboot the +system. + +VI. Correction details + +The following list contains the correction revision numbers for each +affected branch. + +Branch/path Revision +- ------------------------------------------------------------------------- +stable/10/ r339984 +releng/10.4/ r338981 +stable/11/ r339983 +releng/11.1/ r338981 +releng/11.2/ r338981 +- ------------------------------------------------------------------------- + +To see which files were modified by a particular revision, run the +following command, replacing NNNNNN with the revision number, on a +machine with Subversion installed: + +# svn diff -cNNNNNN --summarize svn://svn.freebsd.org/base + +Or visit the following URL, replacing NNNNNN with the revision number: + + + +VII. References + + + +The latest revision of this advisory is available at + +-----BEGIN PGP SIGNATURE----- + +iQKSBAEBCgB9FiEE/A6HiuWv54gCjWNV05eS9J6n5cIFAlutKU5fFIAAAAAALgAo +aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEZD +MEU4NzhBRTVBRkU3ODgwMjhENjM1NUQzOTc5MkY0OUVBN0U1QzIACgkQ05eS9J6n +5cJfGA/3XLR2dunxnQZYQvdpA8k9HA1zHfKFUMbTJqESIZPofvLnFJiw7gwDl0mF +pMC5LCi+k+LIIsXPLzRk/7BUmoCt/hCbD7BOVuiYXhIZy0VgKhaOggSvOXYOsjNl +JTJa5zGsKm4BUNhAkxcJtCO9i+gOShZ2fxiJ9SU7bO/gVl5HoMh56KWTLUBXX2jD +vZfEvxJvllbvk6ST68jb7C0Ix47+idRO2hdfxVLyZfD1PsILIy6JThqKqsbGgqbA ++ma7OnCigxwI0bds4nusi7vNu3IiFuzjBLfV9exW8kcRgyotOsmCfCjSOlOcEJvR +gKcmqZccf1SMGFR336YwGB66xL56QwpgN+UZ/QhmBX15mqI/oAekd0W3fb3OmfvW +bMiDo0MHmtZqiSnQyUOcCPRW5s0l8EHeWCVbjKX1ViqY6e4NdQajrjRUyXnOqcM5 +vtTWAJ+BCc3Acg1V4nkjF7HNCUyGObKZcbDqK7M7p5+i/CFxJkCdKu0x8dsZRHL8 +7V4SL1sb9OkPWjBxyzHuiQNGJfTgknDsIxvBYcdPVukTtGzrWH1skhdWL2O0CNvQ +Quk2YQePQ/X4ICPIB3s+Yao5N8t0FoEM4Hus6nSCpNRyP5XpCaBISHbhG8Ay7yJr +1p0YkV22eQ5KXiNY6Qmof7S0S1p8IZlomO8J8I/yGuwqh2mkkQ== +=uZtl +-----END PGP SIGNATURE----- Added: head/share/security/patches/EN-18:09/ip.patch ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/share/security/patches/EN-18:09/ip.patch Thu Sep 27 19:11:47 2018 (r52312) @@ -0,0 +1,13 @@ +--- sys/netinet6/frag6.c.orig ++++ sys/netinet6/frag6.c +@@ -216,7 +216,9 @@ + int offset = *offp, nxt, i, next; + int first_frag = 0; + int fragoff, frgpartlen; /* must be larger than u_int16_t */ +- uint32_t hash, hashkey[sizeof(struct in6_addr) * 2 + 1], *hashkeyp; ++ uint32_t hashkey[(sizeof(struct in6_addr) * 2 + ++ sizeof(ip6f->ip6f_ident)) / sizeof(uint32_t)]; ++ uint32_t hash, *hashkeyp; + struct ifnet *dstifp; + u_int8_t ecn, ecn0; + #ifdef RSS Added: head/share/security/patches/EN-18:09/ip.patch.asc ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/share/security/patches/EN-18:09/ip.patch.asc Thu Sep 27 19:11:47 2018 (r52312) @@ -0,0 +1,18 @@ +-----BEGIN PGP SIGNATURE----- + +iQKTBAABCgB9FiEE/A6HiuWv54gCjWNV05eS9J6n5cIFAlutKWZfFIAAAAAALgAo +aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEZD +MEU4NzhBRTVBRkU3ODgwMjhENjM1NUQzOTc5MkY0OUVBN0U1QzIACgkQ05eS9J6n +5cK5fQ//cqB5ebX2iYBeKRDL7IfgBaDcojr8x8bDwu2PTRqlXtlq2pUVAkzKynaF +HUoJtvE3xKXkCOw60igjtK1AqWjOyLebUfivM/YykcuBvpiVfs6ZNHsiLCFw+oz9 +pMq4I5jbhizxS4Rdo9ZFMo8Gys6lNMdq9iV6f7rJFD7Ls8sJRi5fi5BR7I08AIBl +VVP3E+0ACOitR9YidRRZ5w4QWYjoZJljMjUlIL023B3VkK+h2uxJy16wLdHv3Tpt +c0DnKyXlM1s0BoCq4qSwFkE2BfutIgsNWgzHHmDDhc6ju9eS96OtZDrok7+knLQr +eBH5WEzXnnrBc+J31LIVVev12uJhntAXRtOau218BYeCnjwln4mBk/y+JqIqLjar +jn4rWEj7lh/PTsmAEulh53mTdyz+tEHSeacNnkR+vuynLGWNUKmFkul4RCLrlP74 +u5qquwkDe3l/6vluGR6tI52RiDiyAuT5s6czH5/mKb/ewWTHj3uFJx9X0J/55Kcp +pBSNuNtzwpjm2bAQy/9n6AYHqfmKvbKoIjIAB+WZwefYrEmAEfaqzchmjfrw5A0a +D8w7IQhljX1CAZ9IcjuUMOWlNSeWdIlGHMZpXM+1MH4nP3RF1JbHGlCyo5WaRHKs +0FLBWGYFN/hvUjY1H1izCCtKeUTDG6y9WnFJW+/VchZZvWFhP24= +=q3dd +-----END PGP SIGNATURE----- Added: head/share/security/patches/EN-18:10/syscall-11.patch ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/share/security/patches/EN-18:10/syscall-11.patch Thu Sep 27 19:11:47 2018 (r52312) @@ -0,0 +1,11 @@ +--- sys/kern/vfs_syscalls.c.orig ++++ sys/kern/vfs_syscalls.c +@@ -600,6 +600,8 @@ + size = count * sizeof(struct statfs); + error = kern_getfsstat(td, &buf, size, &count, UIO_SYSSPACE, + uap->mode); ++ if (buf == NULL) ++ return (EINVAL); + td->td_retval[0] = count; + if (size != 0) { + sp = buf; Added: head/share/security/patches/EN-18:10/syscall-11.patch.asc ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/share/security/patches/EN-18:10/syscall-11.patch.asc Thu Sep 27 19:11:47 2018 (r52312) @@ -0,0 +1,18 @@ +-----BEGIN PGP SIGNATURE----- + +iQKTBAABCgB9FiEE/A6HiuWv54gCjWNV05eS9J6n5cIFAlutKW1fFIAAAAAALgAo +aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEZD +MEU4NzhBRTVBRkU3ODgwMjhENjM1NUQzOTc5MkY0OUVBN0U1QzIACgkQ05eS9J6n +5cLwRxAAnybQwo07WZtP8aLAuOEzXjEJ8rLMKAV80pvIFj27TAxpiIw1cltQsZhb +qHMhYFjnJejgujwBmMEz7rAK97zte71AW4Lm4+I6r2MY8Wniu8OiTHUkYOHlNkWM +iROkSiRRLtPdH0HXk3M5n+BhprDgovOv1xQhu17RLbDYX+9mz5kB2EaRJtnv0JCT +ZfYhin262zaZR0yJ4f5Hug5NphmcbD7VtSD3ZNye2txicJ7330B3iIcpD6YZnkH2 +pJqs4OzLux/xHhQdSMCN5dVtC6M5Gkt6gYDQX6vMoouRw/2o4gcpjye9aV1rkrVd +D3c8iGwdTxyYzUZ++E3OCilx4YbAqmBEXmP4BsiiiO71XHr+oB79+0FQ+U0ZNy7T +zVuc9TJOfOnIDyyz4KL5RcMSFFdNggnYHdCYQZAGk+Xv8aY1ddxmV8M1NBpMvuhS +XQpiWvfoEP5e0pmRfG3OL5XOt9J271BF+gPMRDOAAeDgU/PkWRrHWxAQJtiC6HYl +TEirv16TKpui1nITJj9Q8BBgxMdymEY5SezKdCYeX5PKwsCO9xd0ZRTBhgvVwnCU +e/UTu7vL0ngZ9TFsTVj2A5YsGhDn/7ayYBMwndplF82lpdvPGwhSYmUUpHYBesXi +NjnZjLrpxM+pntbnEcTPLuE7xqIvWsqn6M4DQeRs8+bY8zo9l9k= +=s1wm +-----END PGP SIGNATURE----- Added: head/share/security/patches/EN-18:11/listen-10.patch ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/share/security/patches/EN-18:11/listen-10.patch Thu Sep 27 19:11:47 2018 (r52312) @@ -0,0 +1,260 @@ +--- sys/netinet/tcp_usrreq.c.orig ++++ sys/netinet/tcp_usrreq.c +@@ -328,6 +328,7 @@ + struct inpcb *inp; + struct tcpcb *tp = NULL; + struct sockaddr_in6 *sin6p; ++ u_char vflagsav; + + sin6p = (struct sockaddr_in6 *)nam; + if (nam->sa_len != sizeof (*sin6p)) +@@ -344,6 +345,7 @@ + inp = sotoinpcb(so); + KASSERT(inp != NULL, ("tcp6_usr_bind: inp == NULL")); + INP_WLOCK(inp); ++ vflagsav = inp->inp_vflag; + if (inp->inp_flags & (INP_TIMEWAIT | INP_DROPPED)) { + error = EINVAL; + goto out; +@@ -373,6 +375,8 @@ + error = in6_pcbbind(inp, nam, td->td_ucred); + INP_HASH_WUNLOCK(&V_tcbinfo); + out: ++ if (error != 0) ++ inp->inp_vflag = vflagsav; + TCPDEBUG2(PRU_BIND); + INP_WUNLOCK(inp); + return (error); +@@ -434,6 +438,7 @@ + int error = 0; + struct inpcb *inp; + struct tcpcb *tp = NULL; ++ u_char vflagsav; + + TCPDEBUG0; + inp = sotoinpcb(so); +@@ -443,6 +448,7 @@ + error = EINVAL; + goto out; + } ++ vflagsav = inp->inp_vflag; + tp = intotcpcb(inp); + TCPDEBUG1(); + SOCK_LOCK(so); +@@ -469,6 +475,9 @@ + if (tp->t_flags & TF_FASTOPEN) + tp->t_tfo_pending = tcp_fastopen_alloc_counter(); + #endif ++ if (error != 0) ++ inp->inp_vflag = vflagsav; ++ + out: + TCPDEBUG2(PRU_LISTEN); + INP_WUNLOCK(inp); +@@ -543,6 +552,8 @@ + struct inpcb *inp; + struct tcpcb *tp = NULL; + struct sockaddr_in6 *sin6p; ++ u_int8_t incflagsav; ++ u_char vflagsav; + + TCPDEBUG0; + +@@ -559,6 +570,8 @@ + inp = sotoinpcb(so); + KASSERT(inp != NULL, ("tcp6_usr_connect: inp == NULL")); + INP_WLOCK(inp); ++ vflagsav = inp->inp_vflag; ++ incflagsav = inp->inp_inc.inc_flags; + if (inp->inp_flags & INP_TIMEWAIT) { + error = EADDRINUSE; + goto out; +@@ -584,11 +597,11 @@ + } + + in6_sin6_2_sin(&sin, sin6p); +- inp->inp_vflag |= INP_IPV4; +- inp->inp_vflag &= ~INP_IPV6; + if ((error = prison_remote_ip4(td->td_ucred, + &sin.sin_addr)) != 0) + goto out; ++ inp->inp_vflag |= INP_IPV4; ++ inp->inp_vflag &= ~INP_IPV6; + if ((error = tcp_connect(tp, (struct sockaddr *)&sin, td)) != 0) + goto out; + #ifdef TCP_OFFLOAD +@@ -601,11 +614,11 @@ + goto out; + } + #endif ++ if ((error = prison_remote_ip6(td->td_ucred, &sin6p->sin6_addr)) != 0) ++ goto out; + inp->inp_vflag &= ~INP_IPV4; + inp->inp_vflag |= INP_IPV6; + inp->inp_inc.inc_flags |= INC_ISIPV6; +- if ((error = prison_remote_ip6(td->td_ucred, &sin6p->sin6_addr)) != 0) +- goto out; + if ((error = tcp6_connect(tp, nam, td)) != 0) + goto out; + #ifdef TCP_OFFLOAD +@@ -618,6 +631,15 @@ + error = tcp_output(tp); + + out: ++ /* ++ * If the implicit bind in the connect call fails, restore ++ * the flags we modified. ++ */ ++ if (error != 0 && inp->inp_lport == 0) { ++ inp->inp_vflag = vflagsav; ++ inp->inp_inc.inc_flags = incflagsav; ++ } ++ + TCPDEBUG2(PRU_CONNECT); + INP_WUNLOCK(inp); + return (error); +--- sys/netinet6/sctp6_usrreq.c.orig ++++ sys/netinet6/sctp6_usrreq.c +@@ -608,6 +608,7 @@ + struct sctp_inpcb *inp; + struct in6pcb *inp6; + int error; ++ u_char vflagsav; + + inp = (struct sctp_inpcb *)so->so_pcb; + if (inp == NULL) { +@@ -638,6 +639,7 @@ + } + } + inp6 = (struct in6pcb *)inp; ++ vflagsav = inp6->inp_vflag; + inp6->inp_vflag &= ~INP_IPV4; + inp6->inp_vflag |= INP_IPV6; + if ((addr != NULL) && (SCTP_IPV6_V6ONLY(inp6) == 0)) { +@@ -667,7 +669,7 @@ + inp6->inp_vflag |= INP_IPV4; + inp6->inp_vflag &= ~INP_IPV6; + error = sctp_inpcb_bind(so, (struct sockaddr *)&sin, NULL, p); +- return (error); ++ goto out; + } + #endif + break; +@@ -684,7 +686,8 @@ + if (addr->sa_family == AF_INET) { + /* can't bind v4 addr to v6 only socket! */ + SCTP_LTRACE_ERR_RET(inp, NULL, NULL, SCTP_FROM_SCTP6_USRREQ, EINVAL); +- return (EINVAL); ++ error = EINVAL; ++ goto out; + } + #endif + sin6_p = (struct sockaddr_in6 *)addr; +@@ -693,10 +696,14 @@ + /* can't bind v4-mapped addrs either! */ + /* NOTE: we don't support SIIT */ + SCTP_LTRACE_ERR_RET(inp, NULL, NULL, SCTP_FROM_SCTP6_USRREQ, EINVAL); +- return (EINVAL); ++ error = EINVAL; ++ goto out; + } + } + error = sctp_inpcb_bind(so, addr, NULL, p); ++out: ++ if (error != 0) ++ inp6->inp_vflag = vflagsav; + return (error); + } + +--- sys/netinet6/udp6_usrreq.c.orig ++++ sys/netinet6/udp6_usrreq.c +@@ -947,6 +947,7 @@ + struct inpcb *inp; + struct inpcbinfo *pcbinfo; + int error; ++ u_char vflagsav; + + pcbinfo = get_inpcbinfo(so->so_proto->pr_protocol); + inp = sotoinpcb(so); +@@ -954,6 +955,7 @@ + + INP_WLOCK(inp); + INP_HASH_WLOCK(pcbinfo); ++ vflagsav = inp->inp_vflag; + inp->inp_vflag &= ~INP_IPV4; + inp->inp_vflag |= INP_IPV6; + if ((inp->inp_flags & IN6P_IPV6_V6ONLY) == 0) { +@@ -981,6 +983,8 @@ + #ifdef INET + out: + #endif ++ if (error != 0) ++ inp->inp_vflag = vflagsav; + INP_HASH_WUNLOCK(pcbinfo); + INP_WUNLOCK(inp); + return (error); +@@ -1023,6 +1027,7 @@ + struct inpcbinfo *pcbinfo; + struct sockaddr_in6 *sin6; + int error; ++ u_char vflagsav; + + pcbinfo = get_inpcbinfo(so->so_proto->pr_protocol); + inp = sotoinpcb(so); +@@ -1046,17 +1051,26 @@ + goto out; + } + in6_sin6_2_sin(&sin, sin6); +- inp->inp_vflag |= INP_IPV4; +- inp->inp_vflag &= ~INP_IPV6; + error = prison_remote_ip4(td->td_ucred, &sin.sin_addr); + if (error != 0) + goto out; ++ vflagsav = inp->inp_vflag; ++ inp->inp_vflag |= INP_IPV4; ++ inp->inp_vflag &= ~INP_IPV6; + INP_HASH_WLOCK(pcbinfo); + error = in_pcbconnect(inp, (struct sockaddr *)&sin, + td->td_ucred); + INP_HASH_WUNLOCK(pcbinfo); ++ /* ++ * If connect succeeds, mark socket as connected. If ++ * connect fails and socket is unbound, reset inp_vflag ++ * field. ++ */ + if (error == 0) + soisconnected(so); ++ else if (inp->inp_laddr.s_addr == INADDR_ANY && ++ inp->inp_lport == 0) ++ inp->inp_vflag = vflagsav; + goto out; + } + #endif +@@ -1064,16 +1078,25 @@ + error = EISCONN; + goto out; + } +- inp->inp_vflag &= ~INP_IPV4; +- inp->inp_vflag |= INP_IPV6; + error = prison_remote_ip6(td->td_ucred, &sin6->sin6_addr); + if (error != 0) + goto out; ++ vflagsav = inp->inp_vflag; ++ inp->inp_vflag &= ~INP_IPV4; ++ inp->inp_vflag |= INP_IPV6; + INP_HASH_WLOCK(pcbinfo); + error = in6_pcbconnect(inp, nam, td->td_ucred); + INP_HASH_WUNLOCK(pcbinfo); ++ /* ++ * If connect succeeds, mark socket as connected. If ++ * connect fails and socket is unbound, reset inp_vflag ++ * field. ++ */ + if (error == 0) + soisconnected(so); ++ else if (IN6_IS_ADDR_UNSPECIFIED(&inp->in6p_laddr) && ++ inp->inp_lport == 0) ++ inp->inp_vflag = vflagsav; + out: + INP_WUNLOCK(inp); + return (error); Added: head/share/security/patches/EN-18:11/listen-10.patch.asc ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/share/security/patches/EN-18:11/listen-10.patch.asc Thu Sep 27 19:11:47 2018 (r52312) @@ -0,0 +1,18 @@ +-----BEGIN PGP SIGNATURE----- + +iQKTBAABCgB9FiEE/A6HiuWv54gCjWNV05eS9J6n5cIFAlutKX5fFIAAAAAALgAo +aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEZD +MEU4NzhBRTVBRkU3ODgwMjhENjM1NUQzOTc5MkY0OUVBN0U1QzIACgkQ05eS9J6n +5cLu1Q//dA9SiNzXp7Yn4jdV4DYI9OAOeeqi0yPYNpMjA2YL3/ItEB4SrIE86ELc +9/OuUXZPUaRkvefgOO8IvY/wZKDCHOm94lizn2mstp3JyNLVFaTWimu1QQSaZZCj +bCCVqMVWlYa3ssIUv3wJ8XPf0hDAJ4m+UuMoKG/6YpIsy5AM041RHNYFj881KLRw +4vBioFuoKKQliIksfTgLJjjf6HvKeu9tHnckKrAyZ//sxAsSZ5zfnQbjXwympY8R +n22Om1aXSYQc4Pve4dXY6gLhPcEtIAZKR6L1SOWtHv1RECSK98ePbDTXqQIkpOab +au/WJyjLkZQ6SgIZofGVe9OAb0ibYO5eshgMWmHHDXyFmPAZ7P/XUFWM0C3bN5DA +gQo3sLVJxZ2x6S8/shhK9OWU0pxVFbsewKsqTpHqozhCL/s9obfr81ao2dAGV8pR +l9kT16PZcuWmvqMPgb7AF1eTBzSg4XtGcAEqcwIIuUEnCplCrnaDVaCfATsmu48s +/x8RELtfCBbwGdCcoaCTimQJSe2xVfEI/mO60C1fZCeQCVfsCepgFDfR0HGd/lIq +tCDIgoCFs978IPyApSpJ9IENK+SdA8jxfyPYbR+DrtCP23TIt+n6VISP5KCYRgn0 +mk/h/BV1GxHsM3FonUE3cV+AReRT3lJZHenXKQU3mxZn9C3wpKs= +=1akG +-----END PGP SIGNATURE----- Added: head/share/security/patches/EN-18:11/listen-11.patch ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/share/security/patches/EN-18:11/listen-11.patch Thu Sep 27 19:11:47 2018 (r52312) @@ -0,0 +1,260 @@ +--- sys/netinet/tcp_usrreq.c.orig ++++ sys/netinet/tcp_usrreq.c +@@ -339,6 +339,7 @@ + struct inpcb *inp; + struct tcpcb *tp = NULL; + struct sockaddr_in6 *sin6p; ++ u_char vflagsav; + + sin6p = (struct sockaddr_in6 *)nam; + if (nam->sa_len != sizeof (*sin6p)) +@@ -355,6 +356,7 @@ + inp = sotoinpcb(so); + KASSERT(inp != NULL, ("tcp6_usr_bind: inp == NULL")); + INP_WLOCK(inp); ++ vflagsav = inp->inp_vflag; + if (inp->inp_flags & (INP_TIMEWAIT | INP_DROPPED)) { + error = EINVAL; + goto out; +@@ -384,6 +386,8 @@ + error = in6_pcbbind(inp, nam, td->td_ucred); + INP_HASH_WUNLOCK(&V_tcbinfo); + out: ++ if (error != 0) ++ inp->inp_vflag = vflagsav; + TCPDEBUG2(PRU_BIND); + TCP_PROBE2(debug__user, tp, PRU_BIND); + INP_WUNLOCK(inp); +@@ -447,6 +451,7 @@ + int error = 0; + struct inpcb *inp; + struct tcpcb *tp = NULL; ++ u_char vflagsav; + + TCPDEBUG0; + inp = sotoinpcb(so); +@@ -456,6 +461,7 @@ + error = EINVAL; + goto out; + } ++ vflagsav = inp->inp_vflag; + tp = intotcpcb(inp); + TCPDEBUG1(); + SOCK_LOCK(so); +@@ -482,6 +488,9 @@ + if (tp->t_flags & TF_FASTOPEN) + tp->t_tfo_pending = tcp_fastopen_alloc_counter(); + #endif ++ if (error != 0) ++ inp->inp_vflag = vflagsav; ++ + out: + TCPDEBUG2(PRU_LISTEN); + TCP_PROBE2(debug__user, tp, PRU_LISTEN); +@@ -558,6 +567,8 @@ + struct inpcb *inp; + struct tcpcb *tp = NULL; + struct sockaddr_in6 *sin6p; ++ u_int8_t incflagsav; ++ u_char vflagsav; + + TCPDEBUG0; + +@@ -574,6 +585,8 @@ + inp = sotoinpcb(so); + KASSERT(inp != NULL, ("tcp6_usr_connect: inp == NULL")); + INP_WLOCK(inp); ++ vflagsav = inp->inp_vflag; ++ incflagsav = inp->inp_inc.inc_flags; + if (inp->inp_flags & INP_TIMEWAIT) { + error = EADDRINUSE; + goto out; +@@ -603,11 +616,11 @@ + } + + in6_sin6_2_sin(&sin, sin6p); +- inp->inp_vflag |= INP_IPV4; *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-head@freebsd.org Fri Sep 28 16:20:35 2018 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CB96C10B4254; Fri, 28 Sep 2018 16:20:35 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7C36778F46; Fri, 28 Sep 2018 16:20:35 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 7749A174BB; Fri, 28 Sep 2018 16:20:35 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w8SGKZT2043917; Fri, 28 Sep 2018 16:20:35 GMT (envelope-from ryusuke@FreeBSD.org) Received: (from ryusuke@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w8SGKZuP043916; Fri, 28 Sep 2018 16:20:35 GMT (envelope-from ryusuke@FreeBSD.org) Message-Id: <201809281620.w8SGKZuP043916@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: ryusuke set sender to ryusuke@FreeBSD.org using -f From: Ryusuke SUZUKI Date: Fri, 28 Sep 2018 16:20:35 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52313 - head/ja_JP.eucJP/htdocs/snapshots X-SVN-Group: doc-head X-SVN-Commit-Author: ryusuke X-SVN-Commit-Paths: head/ja_JP.eucJP/htdocs/snapshots X-SVN-Commit-Revision: 52313 X-SVN-Commit-Repository: doc 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.27 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2018 16:20:36 -0000 Author: ryusuke Date: Fri Sep 28 16:20:35 2018 New Revision: 52313 URL: https://svnweb.freebsd.org/changeset/doc/52313 Log: - Merge the following from the English version: r51096 -> r52310 head/ja_JP.eucJP/htdocs/snapshots/index.xml Modified: head/ja_JP.eucJP/htdocs/snapshots/index.xml Modified: head/ja_JP.eucJP/htdocs/snapshots/index.xml ============================================================================== --- head/ja_JP.eucJP/htdocs/snapshots/index.xml Thu Sep 27 19:11:47 2018 (r52312) +++ head/ja_JP.eucJP/htdocs/snapshots/index.xml Fri Sep 28 16:20:35 2018 (r52313) @@ -7,7 +7,7 @@ ]> - + @@ -44,7 +44,7 @@ &rel.head.major;-CURRENT, &rel.current.major;-STABLE および - &rel1.current.major;-STABLE + &rel2.current.major;-STABLE のスナップショットが、 &url.snapshots;<target>/<target_arch>/ 形式の URL にて公開されています。 From owner-svn-doc-head@freebsd.org Sat Sep 29 17:36:55 2018 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 489CE10A600C; Sat, 29 Sep 2018 17:36:55 +0000 (UTC) (envelope-from allanjude@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F3628818BE; Sat, 29 Sep 2018 17:36:54 +0000 (UTC) (envelope-from allanjude@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id EE5B7268EF; Sat, 29 Sep 2018 17:36:54 +0000 (UTC) (envelope-from allanjude@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w8THast3025775; Sat, 29 Sep 2018 17:36:54 GMT (envelope-from allanjude@FreeBSD.org) Received: (from allanjude@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w8THasne025774; Sat, 29 Sep 2018 17:36:54 GMT (envelope-from allanjude@FreeBSD.org) Message-Id: <201809291736.w8THasne025774@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: allanjude set sender to allanjude@FreeBSD.org using -f From: Allan Jude Date: Sat, 29 Sep 2018 17:36:54 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52314 - head/en_US.ISO8859-1/books/porters-handbook/makefiles X-SVN-Group: doc-head X-SVN-Commit-Author: allanjude X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/porters-handbook/makefiles X-SVN-Commit-Revision: 52314 X-SVN-Commit-Repository: doc 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.27 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Sep 2018 17:36:55 -0000 Author: allanjude Date: Sat Sep 29 17:36:54 2018 New Revision: 52314 URL: https://svnweb.freebsd.org/changeset/doc/52314 Log: Fix minor spelling mistake in porters handbook PR: 231799 Submitted by: db 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 Fri Sep 28 16:20:35 2018 (r52313) +++ head/en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml Sat Sep 29 17:36:54 2018 (r52314) @@ -2705,7 +2705,7 @@ v0.7.3-0-gc66c71d - As this is only syntastic sugar above + As this is only syntactic sugar above DISTFILES and MASTER_SITES, the group names must adhere to the restrictions on group names outlined in @@ -3093,7 +3093,7 @@ GL_COMMIT= 9c1669ce60c3f4f5eb43df874d7314483fb3f8a6

      - As this is only syntastic sugar above + As this is only syntactic sugar above DISTFILES and MASTER_SITES, the group names must adhere to the restrictions on group names outlined in