From owner-svn-doc-all@FreeBSD.ORG Sun Feb 10 14:11:02 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7301F934; Sun, 10 Feb 2013 14:11:02 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 66252F02; Sun, 10 Feb 2013 14:11:02 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1AEB2LK085900; Sun, 10 Feb 2013 14:11:02 GMT (envelope-from ryusuke@svn.freebsd.org) Received: (from ryusuke@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1AEB2tj085891; Sun, 10 Feb 2013 14:11:02 GMT (envelope-from ryusuke@svn.freebsd.org) Message-Id: <201302101411.r1AEB2tj085891@svn.freebsd.org> From: Ryusuke SUZUKI Date: Sun, 10 Feb 2013 14:11:02 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40920 - head/ja_JP.eucJP/htdocs X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Feb 2013 14:11:02 -0000 Author: ryusuke Date: Sun Feb 10 14:11:01 2013 New Revision: 40920 URL: http://svnweb.freebsd.org/changeset/doc/40920 Log: - Merge the following from the English version: r29826 -> r40901 head/ja_JP.eucJP/htdocs/mailto.xml Modified: head/ja_JP.eucJP/htdocs/mailto.xml Modified: head/ja_JP.eucJP/htdocs/mailto.xml ============================================================================== --- head/ja_JP.eucJP/htdocs/mailto.xml Sat Feb 9 17:06:24 2013 (r40919) +++ head/ja_JP.eucJP/htdocs/mailto.xml Sun Feb 10 14:11:01 2013 (r40920) @@ -4,7 +4,7 @@ ]> - + @@ -20,6 +20,7 @@

FreeBSD に関する質問は FreeBSD Questions メーリングリスト、 freebsd-questions@FreeBSD.org までどうぞ。

+

メーリングリスト は FreeBSD のユーザにとって主要なサポート手段であり、異なる話題範囲を カバーする多くのメーリングリストがあります。 @@ -49,7 +50,7 @@

担当者一覧

-

広報・渉外担当、セキュリティオフィサ、ポストマスタ、ウェブマスタなど。

+

マーケティング、バグ処理担当、セキュリティオフィサ、ポストマスタ、ウェブマスタなど。

From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 00:01:08 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4A6EE2FC; Mon, 11 Feb 2013 00:01:08 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 248449AA; Mon, 11 Feb 2013 00:01:08 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1B0189V063410; Mon, 11 Feb 2013 00:01:08 GMT (envelope-from rene@svn.freebsd.org) Received: (from rene@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1B018I0063409; Mon, 11 Feb 2013 00:01:08 GMT (envelope-from rene@svn.freebsd.org) Message-Id: <201302110001.r1B018I0063409@svn.freebsd.org> From: Rene Ladan Date: Mon, 11 Feb 2013 00:01:07 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40921 - head/en_US.ISO8859-1/books/arch-handbook/boot X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 00:01:08 -0000 Author: rene Date: Mon Feb 11 00:01:07 2013 New Revision: 40921 URL: http://svnweb.freebsd.org/changeset/doc/40921 Log: Some 'igor -z' improvements. Approved by: gjb (mentor) Modified: head/en_US.ISO8859-1/books/arch-handbook/boot/chapter.xml Modified: head/en_US.ISO8859-1/books/arch-handbook/boot/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/arch-handbook/boot/chapter.xml Sun Feb 10 14:11:01 2013 (r40920) +++ head/en_US.ISO8859-1/books/arch-handbook/boot/chapter.xml Mon Feb 11 00:01:07 2013 (r40921) @@ -184,7 +184,7 @@ Timecounter "i8254" frequency 1193182 H time. As mentioned previously, the INT 0x19 - instruction loads an MBR, i.e. the boot0 + instruction loads an MBR, i.e., the boot0 content, into the memory at address 0x7c00. Taking a look at the file sys/boot/i386/boot0/boot0.S can give a guess at what is happening there - this is the boot @@ -317,7 +317,7 @@ boot2: boot2.ldr boot2.bin ${BTX}/btx/bt link the binary. BTX, which stands for BooT eXtender, is a piece of code that provides a protected mode environment for the program, called the client, that it is linked with. So - boot2 is a BTX client, i.e. it uses the + boot2 is a BTX client, i.e., it uses the service provided by BTX. linker @@ -707,7 +707,7 @@ begin: at a 4Gb boundary. Therefore, the instruction's linear virtual address for this example would just be the value of EIP. Segment registers such as CS, DS etc are the selectors, - i.e. indexes, into GDT (to be more precise, an index is not a + i.e., indexes, into GDT (to be more precise, an index is not a selector itself, but the INDEX field of a selector). FreeBSD's GDT holds descriptors for 15 selectors per CPU: @@ -918,7 +918,7 @@ __asm(".previous"); __asm is. The third __asm instruction marks the end of a section. If a directive with the same section name occurred - before, the content, i.e. the 32-bit value, will be appended + before, the content, i.e., the 32-bit value, will be appended to the existing section, so forming an array of 32-bit pointers. From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 00:02:08 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 264A7359; Mon, 11 Feb 2013 00:02:08 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id DD9429AC; Mon, 11 Feb 2013 00:02:07 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1B027SJ063621; Mon, 11 Feb 2013 00:02:07 GMT (envelope-from rene@svn.freebsd.org) Received: (from rene@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1B027Dd063620; Mon, 11 Feb 2013 00:02:07 GMT (envelope-from rene@svn.freebsd.org) Message-Id: <201302110002.r1B027Dd063620@svn.freebsd.org> From: Rene Ladan Date: Mon, 11 Feb 2013 00:02:07 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40922 - head/en_US.ISO8859-1/books/arch-handbook/driverbasics X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 00:02:08 -0000 Author: rene Date: Mon Feb 11 00:02:07 2013 New Revision: 40922 URL: http://svnweb.freebsd.org/changeset/doc/40922 Log: Some 'igor -z' improvements. Approved by: gjb (mentor) Modified: head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml Modified: head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml Mon Feb 11 00:01:07 2013 (r40921) +++ head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml Mon Feb 11 00:02:07 2013 (r40922) @@ -67,13 +67,14 @@ a running kernel without constantly rebooting to test changes. - The kld interface is used through the following - privileged commands: - kernel modulesloading kernel modulesunloading kernel moduleslisting + + The kld interface is used through the following + privileged commands: + kldload - loads a new kernel module @@ -82,7 +83,6 @@ kldstat - lists the currently loaded modules - Skeleton Layout of a kernel module @@ -152,7 +152,7 @@ KMOD=skeleton - Accessing a device driver + Accessing a Device Driver &unix; provides a common set of system calls for user applications to use. The upper layers of the kernel dispatch @@ -164,7 +164,7 @@ KMOD=skeleton - Creating static device nodes + Creating Static Device Nodes device nodesstatic mknod @@ -176,7 +176,7 @@ KMOD=skeleton - Dynamic device nodes + Dynamic Device Nodes device nodesdynamic devfs From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 00:02:50 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 9BE5A3C5; Mon, 11 Feb 2013 00:02:50 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 6B8B69B5; Mon, 11 Feb 2013 00:02:50 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1B02oE7063774; Mon, 11 Feb 2013 00:02:50 GMT (envelope-from rene@svn.freebsd.org) Received: (from rene@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1B02oed063773; Mon, 11 Feb 2013 00:02:50 GMT (envelope-from rene@svn.freebsd.org) Message-Id: <201302110002.r1B02oed063773@svn.freebsd.org> From: Rene Ladan Date: Mon, 11 Feb 2013 00:02:50 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40923 - head/en_US.ISO8859-1/books/arch-handbook/isa X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 00:02:50 -0000 Author: rene Date: Mon Feb 11 00:02:49 2013 New Revision: 40923 URL: http://svnweb.freebsd.org/changeset/doc/40923 Log: Some 'igor -z' improvements. Approved by: gjb (mentor) Modified: head/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml Modified: head/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml Mon Feb 11 00:02:07 2013 (r40922) +++ head/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml Mon Feb 11 00:02:49 2013 (r40923) @@ -31,7 +31,7 @@ - ISA device drivers + ISA Device Drivers Synopsis @@ -49,7 +49,7 @@ - Basic information + Basic Information A typical ISA driver would need the following include files: @@ -208,7 +208,7 @@ - Device_t pointer + Device_t Pointer Device_t is the pointer type for the device structure. Here we consider only the methods @@ -277,8 +277,8 @@ - Configuration file and the order of identifying and probing - during auto-configuration + Configuration File and the Order of Identifying and Probing + During Auto-Configuration ISAprobing @@ -593,7 +593,7 @@ RF_TIMESHARE - resource may be - time-shared by multiple drivers, i.e. allocated at the + time-shared by multiple drivers, i.e., allocated at the same time by many but activated only by one at any given moment of time. @@ -731,7 +731,7 @@ - Bus memory mapping + Bus Memory Mapping In many cases data is exchanged between the driver and the device through the memory. Two variants are possible: @@ -849,7 +849,7 @@ the future bus_dmamem_alloc() but not bus_dmamap_create() calls. Must be power of 2. If the memory is planned to be used - in non-cascaded DMA mode (i.e. the DMA addresses will be + in non-cascaded DMA mode (i.e., the DMA addresses will be supplied not by the device itself but by the ISA DMA controller) then the boundary must be no larger than 64KB (64*1024) due to the limitations of the DMA From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 00:04:07 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0FAD1431; Mon, 11 Feb 2013 00:04:07 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 01F439BF; Mon, 11 Feb 2013 00:04:07 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1B046mB064037; Mon, 11 Feb 2013 00:04:06 GMT (envelope-from rene@svn.freebsd.org) Received: (from rene@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1B046NS064036; Mon, 11 Feb 2013 00:04:06 GMT (envelope-from rene@svn.freebsd.org) Message-Id: <201302110004.r1B046NS064036@svn.freebsd.org> From: Rene Ladan Date: Mon, 11 Feb 2013 00:04:06 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40924 - head/en_US.ISO8859-1/books/arch-handbook/jail X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 00:04:07 -0000 Author: rene Date: Mon Feb 11 00:04:06 2013 New Revision: 40924 URL: http://svnweb.freebsd.org/changeset/doc/40924 Log: Some 'igor -z' improvements. Approved by: gjb (mentor) Modified: head/en_US.ISO8859-1/books/arch-handbook/jail/chapter.xml Modified: head/en_US.ISO8859-1/books/arch-handbook/jail/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/arch-handbook/jail/chapter.xml Mon Feb 11 00:02:49 2013 (r40923) +++ head/en_US.ISO8859-1/books/arch-handbook/jail/chapter.xml Mon Feb 11 00:04:06 2013 (r40924) @@ -139,7 +139,7 @@ j.ip_number = ntohl(in.s_addr); - Jailing The Process + Jailing the Process Finally, the userland program jails the process. Jail now becomes an imprisoned @@ -224,7 +224,7 @@ SYSCTL_INT(_security_jail, OID_AUTO, mou - &man.jail.2; system call + &man.jail.2; System Call Like all system calls, the &man.jail.2; system call takes two arguments, struct thread *td and @@ -617,7 +617,7 @@ socreate(int dom, struct socket **aso, i contains the port, address, length and domain family of the socket which is to be bound. Basically, this disallows any processes from jail to be able to specify the address - that doesn't belong to the jail in which + that does not belong to the jail in which the calling process exists. /usr/src/sys/netinet/in_pcb.c: From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 00:05:52 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 877294B7; Mon, 11 Feb 2013 00:05:52 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 7A2919D6; Mon, 11 Feb 2013 00:05:52 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1B05qq0064425; Mon, 11 Feb 2013 00:05:52 GMT (envelope-from rene@svn.freebsd.org) Received: (from rene@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1B05q0A064424; Mon, 11 Feb 2013 00:05:52 GMT (envelope-from rene@svn.freebsd.org) Message-Id: <201302110005.r1B05q0A064424@svn.freebsd.org> From: Rene Ladan Date: Mon, 11 Feb 2013 00:05:52 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40925 - head/en_US.ISO8859-1/books/arch-handbook/kobj X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 00:05:52 -0000 Author: rene Date: Mon Feb 11 00:05:51 2013 New Revision: 40925 URL: http://svnweb.freebsd.org/changeset/doc/40925 Log: Some 'igor -z' improvements. Approved by: gjb (mentor) Modified: head/en_US.ISO8859-1/books/arch-handbook/kobj/chapter.xml Modified: head/en_US.ISO8859-1/books/arch-handbook/kobj/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/arch-handbook/kobj/chapter.xml Mon Feb 11 00:04:06 2013 (r40924) +++ head/en_US.ISO8859-1/books/arch-handbook/kobj/chapter.xml Mon Feb 11 00:05:51 2013 (r40925) @@ -123,7 +123,7 @@ KOBJMETHOD(NAME, FUNC) - Creating an interface template + Creating an Interface Template Kernel Objects interface From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 00:06:41 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A10C4522; Mon, 11 Feb 2013 00:06:41 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 8D7EB9E1; Mon, 11 Feb 2013 00:06:41 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1B06ffh064612; Mon, 11 Feb 2013 00:06:41 GMT (envelope-from rene@svn.freebsd.org) Received: (from rene@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1B06fpC064611; Mon, 11 Feb 2013 00:06:41 GMT (envelope-from rene@svn.freebsd.org) Message-Id: <201302110006.r1B06fpC064611@svn.freebsd.org> From: Rene Ladan Date: Mon, 11 Feb 2013 00:06:41 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40926 - head/en_US.ISO8859-1/books/arch-handbook/newbus X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 00:06:41 -0000 Author: rene Date: Mon Feb 11 00:06:40 2013 New Revision: 40926 URL: http://svnweb.freebsd.org/changeset/doc/40926 Log: Some 'igor -z' improvements. Approved by: gjb (mentor) 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 Mon Feb 11 00:05:51 2013 (r40925) +++ head/en_US.ISO8859-1/books/arch-handbook/newbus/chapter.xml Mon Feb 11 00:06:40 2013 (r40926) @@ -64,7 +64,7 @@ A device driver is a software component which provides the interface between the kernel's generic view of a peripheral - (e.g. disk, network adapter) and the actual implementation of + (e.g., disk, network adapter) and the actual implementation of the peripheral. The device driver interface (DDI) is the defined interface between the kernel and the device driver component. @@ -191,7 +191,7 @@ Alpha's ISA bus device. On IA-32, ISA and PCI interrupts are both managed by the top-level nexus device. For both ports, memory and port address space is managed by a single entity - - nexus for IA-32 and the relevant chipset driver on Alpha (e.g. + nexus for IA-32 and the relevant chipset driver on Alpha (e.g., CIA or tsunami). In order to normalize access to memory and port mapped From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 00:07:30 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 12203583; Mon, 11 Feb 2013 00:07:30 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id D51D39E6; Mon, 11 Feb 2013 00:07:29 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1B07TkG064802; Mon, 11 Feb 2013 00:07:29 GMT (envelope-from rene@svn.freebsd.org) Received: (from rene@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1B07TwM064801; Mon, 11 Feb 2013 00:07:29 GMT (envelope-from rene@svn.freebsd.org) Message-Id: <201302110007.r1B07TwM064801@svn.freebsd.org> From: Rene Ladan Date: Mon, 11 Feb 2013 00:07:29 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40927 - head/en_US.ISO8859-1/books/arch-handbook/scsi X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 00:07:30 -0000 Author: rene Date: Mon Feb 11 00:07:29 2013 New Revision: 40927 URL: http://svnweb.freebsd.org/changeset/doc/40927 Log: Some 'igor -z' improvements. Approved by: gjb (mentor) Modified: head/en_US.ISO8859-1/books/arch-handbook/scsi/chapter.xml Modified: head/en_US.ISO8859-1/books/arch-handbook/scsi/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/arch-handbook/scsi/chapter.xml Mon Feb 11 00:06:40 2013 (r40926) +++ head/en_US.ISO8859-1/books/arch-handbook/scsi/chapter.xml Mon Feb 11 00:07:29 2013 (r40927) @@ -69,7 +69,7 @@ - General architecture + General Architecture Common Access Method (CAM) @@ -166,7 +166,7 @@ bus? The answer given in the comments to the CAM code is: either way, as the driver's author prefers. - The arguments are: + The arguments are: action_func - pointer to @@ -226,7 +226,6 @@ depth. It depends on the abilities of the SCSI adapter. - SCSIadapter Finally we register the SCSI buses associated with our SCSI @@ -238,7 +237,7 @@ } If there is one devq structure per - SCSI bus (i.e. we consider a card with multiple buses as + SCSI bus (i.e., we consider a card with multiple buses as multiple cards with one bus each) then the bus number will always be 0, otherwise each bus on the SCSI card should be get a distinct number. Each bus needs its own separate structure @@ -562,7 +561,7 @@ to zero. tag_action - the kind - of tag to use: + of tag to use: CAM_TAG_ACTION_NONE - do not use tags for this @@ -574,7 +573,7 @@ itself - + From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 00:08:09 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4A0FE5E5; Mon, 11 Feb 2013 00:08:09 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 21B559EC; Mon, 11 Feb 2013 00:08:09 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1B089Yn064957; Mon, 11 Feb 2013 00:08:09 GMT (envelope-from rene@svn.freebsd.org) Received: (from rene@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1B089e3064956; Mon, 11 Feb 2013 00:08:09 GMT (envelope-from rene@svn.freebsd.org) Message-Id: <201302110008.r1B089e3064956@svn.freebsd.org> From: Rene Ladan Date: Mon, 11 Feb 2013 00:08:08 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40928 - head/en_US.ISO8859-1/books/arch-handbook/smp X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 00:08:09 -0000 Author: rene Date: Mon Feb 11 00:08:08 2013 New Revision: 40928 URL: http://svnweb.freebsd.org/changeset/doc/40928 Log: Some 'igor -z' improvements. Approved by: gjb (mentor) Modified: head/en_US.ISO8859-1/books/arch-handbook/smp/chapter.xml Modified: head/en_US.ISO8859-1/books/arch-handbook/smp/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/arch-handbook/smp/chapter.xml Mon Feb 11 00:07:29 2013 (r40927) +++ head/en_US.ISO8859-1/books/arch-handbook/smp/chapter.xml Mon Feb 11 00:08:08 2013 (r40928) @@ -125,7 +125,7 @@ - Read Locks versus Write Locks + Read Locks Versus Write Locks read locks write locks @@ -655,7 +655,7 @@ needed. Those items that do not matter if the race is won or lost will not be locked, since they tend to be read all over the place - (e.g. &man.device.get.softc.9;). There will be relatively few + (e.g., &man.device.get.softc.9;). There will be relatively few changes to the newbus data structures, so a single lock should be sufficient and not impose a performance penalty. From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 00:08:44 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 45FC6644; Mon, 11 Feb 2013 00:08:44 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 087359F0; Mon, 11 Feb 2013 00:08:44 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1B08hSG065091; Mon, 11 Feb 2013 00:08:43 GMT (envelope-from rene@svn.freebsd.org) Received: (from rene@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1B08hMG065090; Mon, 11 Feb 2013 00:08:43 GMT (envelope-from rene@svn.freebsd.org) Message-Id: <201302110008.r1B08hMG065090@svn.freebsd.org> From: Rene Ladan Date: Mon, 11 Feb 2013 00:08:43 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40929 - head/en_US.ISO8859-1/books/arch-handbook/sound X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 00:08:44 -0000 Author: rene Date: Mon Feb 11 00:08:43 2013 New Revision: 40929 URL: http://svnweb.freebsd.org/changeset/doc/40929 Log: Some 'igor -z' improvements. Approved by: gjb (mentor) Modified: head/en_US.ISO8859-1/books/arch-handbook/sound/chapter.xml Modified: head/en_US.ISO8859-1/books/arch-handbook/sound/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/arch-handbook/sound/chapter.xml Mon Feb 11 00:08:08 2013 (r40928) +++ head/en_US.ISO8859-1/books/arch-handbook/sound/chapter.xml Mon Feb 11 00:08:43 2013 (r40929) @@ -17,7 +17,7 @@ - Sound subsystem + Sound Subsystem Introduction @@ -96,7 +96,7 @@ - Probing, attaching, etc. + Probing, Attaching, etc. Sound drivers probe and attach in almost the same way as any hardware driver module. You might want to look at the pcm. - The CHANNEL interface + The CHANNEL Interface - Common notes for function parameters + Common Notes for Function Parameters Sound drivers usually have a private data structure to describe their device, and one structure for each play and @@ -234,7 +234,7 @@ - Overview of data transfer operations + Overview of Data Transfer Operations For sound data transfers, the pcm core and the sound drivers @@ -521,7 +521,7 @@ - More functions + More Functions channel_reset(), channel_resetdone(), and @@ -535,7 +535,7 @@ - The MIXER interface + The MIXER Interface mixer_init @@ -656,7 +656,7 @@ - The AC97 interface + The AC97 Interface AC97 From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 00:09:26 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 0F98D6A8; Mon, 11 Feb 2013 00:09:26 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id DAC329F5; Mon, 11 Feb 2013 00:09:25 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1B09P1v065257; Mon, 11 Feb 2013 00:09:25 GMT (envelope-from rene@svn.freebsd.org) Received: (from rene@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1B09PTM065256; Mon, 11 Feb 2013 00:09:25 GMT (envelope-from rene@svn.freebsd.org) Message-Id: <201302110009.r1B09PTM065256@svn.freebsd.org> From: Rene Ladan Date: Mon, 11 Feb 2013 00:09:25 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40930 - head/en_US.ISO8859-1/books/arch-handbook/usb X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 00:09:26 -0000 Author: rene Date: Mon Feb 11 00:09:24 2013 New Revision: 40930 URL: http://svnweb.freebsd.org/changeset/doc/40930 Log: Some 'igor -z' improvements. Approved by: gjb (mentor) 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 Mon Feb 11 00:08:43 2013 (r40929) +++ head/en_US.ISO8859-1/books/arch-handbook/usb/chapter.xml Mon Feb 11 00:09:24 2013 (r40930) @@ -300,7 +300,7 @@ USB Device Information - Device configuration information + Device Configuration Information Each device provides different levels of configuration information. Each device has one or more configurations, of @@ -466,7 +466,7 @@ - Device probe and attach + Device Probe and Attach USBprobe After the notification by the hub that a new device has been @@ -506,7 +506,7 @@ attached. - Device disconnect and detach + Device Disconnect and Detach USBdisconnect A device driver should expect to receive errors during any From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 00:10:03 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C02B970A; Mon, 11 Feb 2013 00:10:03 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 981549FB; Mon, 11 Feb 2013 00:10:03 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1B0A2TX065457; Mon, 11 Feb 2013 00:10:02 GMT (envelope-from rene@svn.freebsd.org) Received: (from rene@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1B0A2ew065456; Mon, 11 Feb 2013 00:10:02 GMT (envelope-from rene@svn.freebsd.org) Message-Id: <201302110010.r1B0A2ew065456@svn.freebsd.org> From: Rene Ladan Date: Mon, 11 Feb 2013 00:10:02 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40931 - head/en_US.ISO8859-1/books/arch-handbook/vm X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 00:10:03 -0000 Author: rene Date: Mon Feb 11 00:10:02 2013 New Revision: 40931 URL: http://svnweb.freebsd.org/changeset/doc/40931 Log: Some 'igor -z' improvements. Approved by: gjb (mentor) Modified: head/en_US.ISO8859-1/books/arch-handbook/vm/chapter.xml Modified: head/en_US.ISO8859-1/books/arch-handbook/vm/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/arch-handbook/vm/chapter.xml Mon Feb 11 00:09:24 2013 (r40930) +++ head/en_US.ISO8859-1/books/arch-handbook/vm/chapter.xml Mon Feb 11 00:10:02 2013 (r40931) @@ -20,8 +20,8 @@ Virtual Memory System - Management of physical - memory—<literal>vm_page_t</literal> + Management of Physical + Memory—<literal>vm_page_t</literal> virtual memory physical memory @@ -73,7 +73,7 @@ FreeBSD dynamically tunes its paging queues and attempts to maintain reasonable ratios of pages in the various queues as well as - attempts to maintain a reasonable breakdown of clean vs. dirty pages. + attempts to maintain a reasonable breakdown of clean versus dirty pages. The amount of rebalancing that occurs depends on the system's memory load. This rebalancing is implemented by the pageout daemon and involves laundering dirty pages (syncing them with their backing @@ -87,8 +87,8 @@ - The unified buffer - cache—<literal>vm_object_t</literal> + The Unified Buffer + Cache—<literal>vm_object_t</literal> unified buffer cache vm_object_t structure @@ -199,7 +199,7 @@ - Tuning the FreeBSD VM system + Tuning the FreeBSD VM System A concerted effort has been made to make the FreeBSD kernel dynamically tune itself. Typically you do not need to mess with From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 00:42:07 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E2E64C3E; Mon, 11 Feb 2013 00:42:07 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id A2D80AF1; Mon, 11 Feb 2013 00:42:07 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.6/8.14.6) with ESMTP id r1B0g1l3015430; Sun, 10 Feb 2013 17:42:01 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.6/8.14.6/Submit) with ESMTP id r1B0g1AN015427; Sun, 10 Feb 2013 17:42:01 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Sun, 10 Feb 2013 17:42:01 -0700 (MST) From: Warren Block To: Rene Ladan Subject: Re: svn commit: r40923 - head/en_US.ISO8859-1/books/arch-handbook/isa In-Reply-To: <201302110002.r1B02oed063773@svn.freebsd.org> Message-ID: References: <201302110002.r1B02oed063773@svn.freebsd.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Sun, 10 Feb 2013 17:42:01 -0700 (MST) Cc: svn-doc-head@freebsd.org, svn-doc-all@freebsd.org, doc-committers@freebsd.org X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 00:42:08 -0000 On Mon, 11 Feb 2013, Rene Ladan wrote: > Modified: > head/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml > > Modified: head/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml > ============================================================================== > --- head/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml Mon Feb 11 00:02:07 2013 (r40922) > +++ head/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml Mon Feb 11 00:02:49 2013 (r40923) > @@ -31,7 +31,7 @@ > > > > - ISA device drivers > + ISA Device Drivers > > > Synopsis > @@ -49,7 +49,7 @@ > > > > - Basic information > + Basic Information > > A typical ISA driver would need the following include > files: > @@ -208,7 +208,7 @@ > > > > - Device_t pointer > + Device_t Pointer > > Device_t is the pointer type for > the device structure. Here we consider only the methods Both of these two changes should really be device_t, with the lower case "d" and the tags. From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 03:22:07 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 47D6329C; Mon, 11 Feb 2013 03:22:07 +0000 (UTC) (envelope-from imp@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 37E9A2EA; Mon, 11 Feb 2013 03:22:07 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1B3M7TI025631; Mon, 11 Feb 2013 03:22:07 GMT (envelope-from imp@svn.freebsd.org) Received: (from imp@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1B3M7eV025630; Mon, 11 Feb 2013 03:22:07 GMT (envelope-from imp@svn.freebsd.org) Message-Id: <201302110322.r1B3M7eV025630@svn.freebsd.org> From: Warner Losh Date: Mon, 11 Feb 2013 03:22:07 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40932 - head/en_US.ISO8859-1/books/arch-handbook/pccard X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 03:22:07 -0000 Author: imp Date: Mon Feb 11 03:22:06 2013 New Revision: 40932 URL: http://svnweb.freebsd.org/changeset/doc/40932 Log: Delete two paragraphs that are no longer relevant... Modified: head/en_US.ISO8859-1/books/arch-handbook/pccard/chapter.xml Modified: head/en_US.ISO8859-1/books/arch-handbook/pccard/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/arch-handbook/pccard/chapter.xml Mon Feb 11 00:10:02 2013 (r40931) +++ head/en_US.ISO8859-1/books/arch-handbook/pccard/chapter.xml Mon Feb 11 03:22:06 2013 (r40932) @@ -315,15 +315,6 @@ product BUFFALO WLI_CF_S11G 0x030b BUFFA product BUFFALO WLI2_CF_S11G 0x030c BUFFALO AirStation ultra 802.11b CF - At present, there is a - manual step to regenerate - pccarddevs.h, used to convey these - identifiers to the client driver. The following steps must be - done before you can use them in the driver: - - &prompt.root; cd src/sys/dev/pccard -&prompt.root; make -f Makefile.pccarddevs - Once these steps are complete, the card can be added to the driver. That is a simple operation of adding one line: From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 03:26:04 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1B1BF30F; Mon, 11 Feb 2013 03:26:04 +0000 (UTC) (envelope-from pclin@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id E668E2FB; Mon, 11 Feb 2013 03:26:03 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1B3Q3oW026162; Mon, 11 Feb 2013 03:26:03 GMT (envelope-from pclin@svn.freebsd.org) Received: (from pclin@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1B3Q27p026152; Mon, 11 Feb 2013 03:26:02 GMT (envelope-from pclin@svn.freebsd.org) Message-Id: <201302110326.r1B3Q27p026152@svn.freebsd.org> From: Po-Chien Lin Date: Mon, 11 Feb 2013 03:26:02 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40933 - in head: en_US.ISO8859-1/articles/contributors share/pgpkeys share/xml X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 03:26:04 -0000 Author: pclin (ports committer) Date: Mon Feb 11 03:26:01 2013 New Revision: 40933 URL: http://svnweb.freebsd.org/changeset/doc/40933 Log: It's my first commit to FreeBSD! Glad to join the cool project :) Approved by: swills (mentor) Added: head/share/pgpkeys/pclin.key (contents, props changed) Modified: head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml head/en_US.ISO8859-1/articles/contributors/contrib.committers.xml head/share/pgpkeys/pgpkeys-developers.xml head/share/pgpkeys/pgpkeys.ent head/share/xml/authors.ent head/share/xml/developers.ent head/share/xml/news.xml Modified: head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml ============================================================================== --- head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Mon Feb 11 03:22:06 2013 (r40932) +++ head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Mon Feb 11 03:26:01 2013 (r40933) @@ -8385,11 +8385,6 @@ - Po-Chien Lin - linpc@cs.nctu.edu.tw - - - Pomegranate daver@flag.blackened.net Modified: head/en_US.ISO8859-1/articles/contributors/contrib.committers.xml ============================================================================== --- head/en_US.ISO8859-1/articles/contributors/contrib.committers.xml Mon Feb 11 03:22:06 2013 (r40932) +++ head/en_US.ISO8859-1/articles/contributors/contrib.committers.xml Mon Feb 11 03:26:01 2013 (r40933) @@ -844,6 +844,10 @@ + &a.pclin; + + + &a.yzlin; Added: head/share/pgpkeys/pclin.key ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/share/pgpkeys/pclin.key Mon Feb 11 03:26:01 2013 (r40933) @@ -0,0 +1,76 @@ + + + +uid Po-Chien Lin +sub 4096R/F31280BA 2013-02-05 +]]> + Modified: head/share/pgpkeys/pgpkeys-developers.xml ============================================================================== --- head/share/pgpkeys/pgpkeys-developers.xml Mon Feb 11 03:22:06 2013 (r40932) +++ head/share/pgpkeys/pgpkeys-developers.xml Mon Feb 11 03:26:01 2013 (r40933) @@ -1031,6 +1031,11 @@ &pgpkey.clive; + + &a.pclin; + &pgpkey.pclin; + + &a.yzlin; &pgpkey.yzlin; Modified: head/share/pgpkeys/pgpkeys.ent ============================================================================== --- head/share/pgpkeys/pgpkeys.ent Mon Feb 11 03:22:06 2013 (r40932) +++ head/share/pgpkeys/pgpkeys.ent Mon Feb 11 03:26:01 2013 (r40933) @@ -286,6 +286,7 @@ + Modified: head/share/xml/authors.ent ============================================================================== --- head/share/xml/authors.ent Mon Feb 11 03:22:06 2013 (r40932) +++ head/share/xml/authors.ent Mon Feb 11 03:26:01 2013 (r40933) @@ -1020,6 +1020,8 @@ pb@FreeBSD.org"> +pclin@FreeBSD.org"> + pdeuskar@FreeBSD.org"> pds@FreeBSD.org"> Modified: head/share/xml/developers.ent ============================================================================== --- head/share/xml/developers.ent Mon Feb 11 03:22:06 2013 (r40932) +++ head/share/xml/developers.ent Mon Feb 11 03:26:01 2013 (r40933) @@ -493,6 +493,7 @@ $FreeBSD$ + Modified: head/share/xml/news.xml ============================================================================== --- head/share/xml/news.xml Mon Feb 11 03:22:06 2013 (r40932) +++ head/share/xml/news.xml Mon Feb 11 03:26:01 2013 (r40933) @@ -31,6 +31,19 @@ 2013 + 2 + + + 10 + + +

New committer: + Po-Chien Lin (ports)

+ + + + + 1 From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 05:26:23 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B56B3F57; Mon, 11 Feb 2013 05:26:23 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id A2BD47A2; Mon, 11 Feb 2013 05:26:23 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1B5QNjO061679; Mon, 11 Feb 2013 05:26:23 GMT (envelope-from ryusuke@svn.freebsd.org) Received: (from ryusuke@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1B5QNrp061678; Mon, 11 Feb 2013 05:26:23 GMT (envelope-from ryusuke@svn.freebsd.org) Message-Id: <201302110526.r1B5QNrp061678@svn.freebsd.org> From: Ryusuke SUZUKI Date: Mon, 11 Feb 2013 05:26:23 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40934 - head/ja_JP.eucJP/share/xml X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 05:26:23 -0000 Author: ryusuke Date: Mon Feb 11 05:26:22 2013 New Revision: 40934 URL: http://svnweb.freebsd.org/changeset/doc/40934 Log: - Merge the following from the English version: r40903 -> r40933 head/ja_JP.eucJP/share/xml/news.xml Modified: head/ja_JP.eucJP/share/xml/news.xml Modified: head/ja_JP.eucJP/share/xml/news.xml ============================================================================== --- head/ja_JP.eucJP/share/xml/news.xml Mon Feb 11 03:26:01 2013 (r40933) +++ head/ja_JP.eucJP/share/xml/news.xml Mon Feb 11 05:26:22 2013 (r40934) @@ -20,7 +20,7 @@ the contents of will be preferred over <p>. $FreeBSD$ - Original revision: r40903 + Original revision: r40933 --> <news> <cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS"> @@ -31,6 +31,19 @@ <name>2013</name> <month> + <name>2</name> + + <day> + <name>10</name> + + <event> + <p>新コミッタ就任: + <a href="mailto:pclin@FreeBSD.org">Po-Chien Lin</a> (ports)</p> + </event> + </day> + </month> + + <month> <name>1</name> <day> From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 10:53:20 2013 Return-Path: <owner-svn-doc-all@FreeBSD.ORG> Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DA779A71; Mon, 11 Feb 2013 10:53:20 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id C8BB61A8F; Mon, 11 Feb 2013 10:53:20 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1BArKgj060132; Mon, 11 Feb 2013 10:53:20 GMT (envelope-from rene@svn.freebsd.org) Received: (from rene@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1BArKU0060131; Mon, 11 Feb 2013 10:53:20 GMT (envelope-from rene@svn.freebsd.org) Message-Id: <201302111053.r1BArKU0060131@svn.freebsd.org> From: Rene Ladan <rene@FreeBSD.org> Date: Mon, 11 Feb 2013 10:53:20 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40935 - head/en_US.ISO8859-1/books/arch-handbook/isa X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" <svn-doc-all.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-all> List-Post: <mailto:svn-doc-all@freebsd.org> List-Help: <mailto:svn-doc-all-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=subscribe> X-List-Received-Date: Mon, 11 Feb 2013 10:53:20 -0000 Author: rene Date: Mon Feb 11 10:53:20 2013 New Revision: 40935 URL: http://svnweb.freebsd.org/changeset/doc/40935 Log: Wrap a device_t instance in <structname> tags and fix a false positive from igor. Submitted by: wblock Approved by: gjb (mentor) Modified: head/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml Modified: head/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml Mon Feb 11 05:26:22 2013 (r40934) +++ head/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml Mon Feb 11 10:53:20 2013 (r40935) @@ -208,9 +208,9 @@ </sect1> <sect1 id="isa-driver-device-t"> - <title>Device_t Pointer + <structname>device_t</structname> Pointer - Device_t is the pointer type for + device_t is the pointer type for the device structure. Here we consider only the methods interesting from the device driver writer's standpoint. The methods to manipulate values in the device structure From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 12:18:24 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4D0EBE34; Mon, 11 Feb 2013 12:18:24 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 318CC319; Mon, 11 Feb 2013 12:18:24 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1BCIOWh085699; Mon, 11 Feb 2013 12:18:24 GMT (envelope-from ryusuke@svn.freebsd.org) Received: (from ryusuke@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1BCIOer085698; Mon, 11 Feb 2013 12:18:24 GMT (envelope-from ryusuke@svn.freebsd.org) Message-Id: <201302111218.r1BCIOer085698@svn.freebsd.org> From: Ryusuke SUZUKI Date: Mon, 11 Feb 2013 12:18:24 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40936 - head/ja_JP.eucJP/books/handbook/advanced-networking X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 12:18:24 -0000 Author: ryusuke Date: Mon Feb 11 12:18:23 2013 New Revision: 40936 URL: http://svnweb.freebsd.org/changeset/doc/40936 Log: - Merge the following from the English version: r20021 -> r20104 head/ja_JP.eucJP/books/handbook/advanced-networking/chapter.xml Submitted by: Tatsuya Yagi , ryusuke Modified: head/ja_JP.eucJP/books/handbook/advanced-networking/chapter.xml Modified: head/ja_JP.eucJP/books/handbook/advanced-networking/chapter.xml ============================================================================== --- head/ja_JP.eucJP/books/handbook/advanced-networking/chapter.xml Mon Feb 11 10:53:20 2013 (r40935) +++ head/ja_JP.eucJP/books/handbook/advanced-networking/chapter.xml Mon Feb 11 12:18:23 2013 (r40936) @@ -3,7 +3,7 @@ The FreeBSD Documentation Project The FreeBSD Japanese Documentation Project - Original revision: r20021 + Original revision: r20104 $FreeBSD$ --> @@ -6511,6 +6511,26 @@ natd_flags="" natd -interface fxp0 が実行されます。 これは手動でも実行できます。 + + オプションの定義に &man.natd.8; + のコンフィグレーションファイルを使うこともできます。 + この場合には、/etc/rc.conf に以下の行を追加し、 + コンフィグレーションファイルを定義してください。 + + natd_flags="-f /etc/natd.conf" + + /etc/natd.conf + ファイルでは、一行ごとにオプションを設定します。たとえば、 + 次節の例では以下のような行を含むファイルを用意してください。 + + redirect_port tcp 192.168.0.2:6667 6667 +redirect_port tcp 192.168.0.3:80 80 + + コンフィグレーションファイルに関する、より詳細な情報については、 + &man.natd.8; マニュアルページの + オプションを調べてください。 + + LAN にぶら下がっているマシンおよびインタフェースのそれぞれには RFC 1918 で定義されているプライベートネットワーク空間の @@ -6577,8 +6597,8 @@ natd_flags="" これらのオプションは &man.natd.8; を直接実行するか、 /etc/rc.conf 内の - natd_flags="" - オプションに指定して使用できます。 + natd_flags="" オプションで設定するか、 + もしくはコンフィグレーションファイルから渡してください。 設定オプションの詳細については &man.natd.8; をご覧ください。 @@ -6636,8 +6656,9 @@ natd_flags="" と同様に、これらの引数は /etc/rc.conf 内の - natd_flags="" - オプションで指定できます。アドレス転送では、 + natd_flags="" オプションで設定するか、 + コンフィグレーションファイルから渡すことで指定できます。 + アドレス転送では、 特定の IP アドレスで受け取られたデータはすべて転送されるので、 port 転送は必要ありません。 From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 13:19:12 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7644A9F7; Mon, 11 Feb 2013 13:19:12 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 3E3AE899; Mon, 11 Feb 2013 13:19:12 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1BDJCZ4004280; Mon, 11 Feb 2013 13:19:12 GMT (envelope-from linimon@svn.freebsd.org) Received: (from linimon@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1BDJCXn004279; Mon, 11 Feb 2013 13:19:12 GMT (envelope-from linimon@svn.freebsd.org) Message-Id: <201302111319.r1BDJCXn004279@svn.freebsd.org> From: Mark Linimon Date: Mon, 11 Feb 2013 13:19:12 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40937 - head/en_US.ISO8859-1/articles/portbuild X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 13:19:12 -0000 Author: linimon Date: Mon Feb 11 13:19:11 2013 New Revision: 40937 URL: http://svnweb.freebsd.org/changeset/doc/40937 Log: Make it a bit more clear what SRCBUILD_USER does. Modified: head/en_US.ISO8859-1/articles/portbuild/article.xml Modified: head/en_US.ISO8859-1/articles/portbuild/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/portbuild/article.xml Mon Feb 11 12:18:23 2013 (r40936) +++ head/en_US.ISO8859-1/articles/portbuild/article.xml Mon Feb 11 13:19:11 2013 (r40937) @@ -2524,8 +2524,9 @@ zfs destroy -r a/snap/src-o - Similarly, create a user to own the svn - repository, such as srcbuild. It should have the + Similarly, create a user to own the administration functions + and manage the svn + repositories, such as srcbuild. It should have the '*' password. From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 13:30:30 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 68646E95; Mon, 11 Feb 2013 13:30:30 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 5B107943; Mon, 11 Feb 2013 13:30:30 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1BDUULw008931; Mon, 11 Feb 2013 13:30:30 GMT (envelope-from linimon@svn.freebsd.org) Received: (from linimon@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1BDUUYt008930; Mon, 11 Feb 2013 13:30:30 GMT (envelope-from linimon@svn.freebsd.org) Message-Id: <201302111330.r1BDUUYt008930@svn.freebsd.org> From: Mark Linimon Date: Mon, 11 Feb 2013 13:30:30 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40938 - head/en_US.ISO8859-1/articles/portbuild X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 13:30:30 -0000 Author: linimon Date: Mon Feb 11 13:30:29 2013 New Revision: 40938 URL: http://svnweb.freebsd.org/changeset/doc/40938 Log: More work to support the split of PORTBUILD_USER into SRCBUILD_USER: - remove the old description of the internals of the mkportbuild script. They are insufficient for the new world. - start refactoring to indicate which configuration variables move from portbuild/conf/server.conf to portbuild/admin/conf/admin.conf. WIP. Modified: head/en_US.ISO8859-1/articles/portbuild/article.xml Modified: head/en_US.ISO8859-1/articles/portbuild/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/portbuild/article.xml Mon Feb 11 13:19:11 2013 (r40937) +++ head/en_US.ISO8859-1/articles/portbuild/article.xml Mon Feb 11 13:30:29 2013 (r40938) @@ -2736,41 +2736,26 @@ sysutils/zfs-stats &prompt.root; sh /home/portbuild/tmp/mkportbuild - This will accomplish all the following 5 steps: + This will accomplish all the following steps: - Create the portbuild directory: - - &prompt.root; mkdir -p ${ZFS_MOUNTPOINT}/portbuild + Create the portbuild directory Create and mount a new zfs - filesystem on it: - - zfs create -o mountpoint=${ZFS_MOUNTPOINT}/portbuild ${ZFS_VOLUME}/portbuild + filesystem on it - Set up the directory: - - &prompt.root; chown ${PORTBUILD_USER}:${PORTBUILD_USER} ${ZFS_MOUNTPOINT}/portbuild -&prompt.root; chmod 775 ${ZFS_MOUNTPOINT}/portbuild -&prompt.root; ln -sf ${ZFS_MOUNTPOINT}/portbuild /var/portbuild - - - The ln is necessary due to a number - of hardcoded paths. This is a bug. - + Set up the directory Set up the initial repository: - - &prompt.user; svn checkout ${VCS_REPOSITORY}/base/projects/portbuild ${ZFS_MOUNTPOINT}/portbuild @@ -2778,14 +2763,33 @@ sysutils/zfs-stats Set up the zfs permission sets. + + + Split ownerships of subdirectories such that + PORTBUILD_USER owns, and + only owns, files that are used to manage builds and + interact with slaves. The more trustable user + SRCBUILD_USER now owns + everything else. + - - Configuring the <application>portbuild</application> files + + Configuring the <application>srcbuild</application>-owned files + + + + (in process of being refactored) + + + + + + Configuring the <application>portbuild</application>-owned files From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 13:32:37 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 6EEC47C; Mon, 11 Feb 2013 13:32:37 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 56FC396C; Mon, 11 Feb 2013 13:32:37 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1BDWbA8009368; Mon, 11 Feb 2013 13:32:37 GMT (envelope-from linimon@svn.freebsd.org) Received: (from linimon@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1BDWbwU009367; Mon, 11 Feb 2013 13:32:37 GMT (envelope-from linimon@svn.freebsd.org) Message-Id: <201302111332.r1BDWbwU009367@svn.freebsd.org> From: Mark Linimon Date: Mon, 11 Feb 2013 13:32:37 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40939 - head/en_US.ISO8859-1/articles/portbuild X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 13:32:37 -0000 Author: linimon Date: Mon Feb 11 13:32:36 2013 New Revision: 40939 URL: http://svnweb.freebsd.org/changeset/doc/40939 Log: Forgotten from last commit: remove something that is now a major lie. Modified: head/en_US.ISO8859-1/articles/portbuild/article.xml Modified: head/en_US.ISO8859-1/articles/portbuild/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/portbuild/article.xml Mon Feb 11 13:30:29 2013 (r40938) +++ head/en_US.ISO8859-1/articles/portbuild/article.xml Mon Feb 11 13:32:36 2013 (r40939) @@ -2708,7 +2708,7 @@ sysutils/zfs-stats We will define a zfs permission set below, so that the - portbuild user may administer this + srcbuild user may administer this volume without having to have root privileges. From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 13:46:22 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 65643B43; Mon, 11 Feb 2013 13:46:22 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 57B2EDA6; Mon, 11 Feb 2013 13:46:22 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1BDkMft012788; Mon, 11 Feb 2013 13:46:22 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1BDkMgL012787; Mon, 11 Feb 2013 13:46:22 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201302111346.r1BDkMgL012787@svn.freebsd.org> From: Eitan Adler Date: Mon, 11 Feb 2013 13:46:22 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40940 - head/en_US.ISO8859-1/htdocs/internal X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 13:46:22 -0000 Author: eadler Date: Mon Feb 11 13:46:21 2013 New Revision: 40940 URL: http://svnweb.freebsd.org/changeset/doc/40940 Log: Feed the screen pixies by sending 404 links to /dev/null Approved by: bcr (mentor) Modified: head/en_US.ISO8859-1/htdocs/internal/internal.xml Modified: head/en_US.ISO8859-1/htdocs/internal/internal.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/internal/internal.xml Mon Feb 11 13:32:36 2013 (r40939) +++ head/en_US.ISO8859-1/htdocs/internal/internal.xml Mon Feb 11 13:46:21 2013 (r40940) @@ -50,11 +50,6 @@ the globe, there have to be some By following the links, one will find a list of them, as well as explanations of who is responsible for what.

-

Here are some -personal homepages -hosted at FreeBSD.org, as well as some -photos from social events.

-

You can read here core's Hat Term Limits Policy and some guidelines from &a.imp; on how to work with hats.

From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 13:46:24 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id BB0B9B46; Mon, 11 Feb 2013 13:46:24 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id AD7BCDA8; Mon, 11 Feb 2013 13:46:24 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1BDkOcj012824; Mon, 11 Feb 2013 13:46:24 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1BDkOKe012823; Mon, 11 Feb 2013 13:46:24 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201302111346.r1BDkOKe012823@svn.freebsd.org> From: Eitan Adler Date: Mon, 11 Feb 2013 13:46:24 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40941 - head/en_US.ISO8859-1/books/arch-handbook/driverbasics X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 13:46:24 -0000 Author: eadler Date: Mon Feb 11 13:46:24 2013 New Revision: 40941 URL: http://svnweb.freebsd.org/changeset/doc/40941 Log: Fix whitespace Translators can ignore Approved by: bcr (mentor) Modified: head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml Modified: head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml Mon Feb 11 13:46:21 2013 (r40940) +++ head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml Mon Feb 11 13:46:24 2013 (r40941) @@ -9,16 +9,16 @@ - Murray - Stokely - Written by + Murray + Stokely + Written by - Jörg - Wunsch - Based on intro(4) manual page by + Jörg + Wunsch + Based on intro(4) manual page by @@ -398,6 +398,7 @@ Closing device "echo". Block Devices (Are Gone) block devices + Other &unix; systems may support a second type of disk device known as block devices. Block devices are disk devices for which the kernel provides caching. This caching makes From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 13:46:27 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 147D7B47; Mon, 11 Feb 2013 13:46:27 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id E2854DA9; Mon, 11 Feb 2013 13:46:26 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1BDkQTW012860; Mon, 11 Feb 2013 13:46:26 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1BDkQXD012859; Mon, 11 Feb 2013 13:46:26 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201302111346.r1BDkQXD012859@svn.freebsd.org> From: Eitan Adler Date: Mon, 11 Feb 2013 13:46:26 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40942 - head/en_US.ISO8859-1/books/arch-handbook/driverbasics X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 13:46:27 -0000 Author: eadler Date: Mon Feb 11 13:46:26 2013 New Revision: 40942 URL: http://svnweb.freebsd.org/changeset/doc/40942 Log: Fix igor nit picks Approved by: bcr (mentor) Modified: head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml Modified: head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml Mon Feb 11 13:46:24 2013 (r40941) +++ head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml Mon Feb 11 13:46:26 2013 (r40942) @@ -72,8 +72,7 @@ kernel modulesunloading kernel moduleslisting - The kld interface is used through the following - privileged commands: + The kld interface is used through: kldload - loads a new kernel @@ -135,17 +134,17 @@ DECLARE_MODULE(skeleton, skel_mod, SI_SU Makefile - FreeBSD provides a makefile include that you can use to - quickly compile your kernel addition. + FreeBSD provides a makefile include to + quickly compile a kernel addition. SRCS=skeleton.c KMOD=skeleton .include <bsd.kmod.mk> - Simply running make with this makefile + Running make with this makefile will create a file skeleton.ko that can - be loaded into your system by typing: + be loaded into the kernel by typing: &prompt.root; kldload -v ./skeleton.ko @@ -201,8 +200,8 @@ KMOD=skeleton the source tree. This simple example pseudo-device remembers whatever values - you write to it and can then supply them back to you when you - read from it. + that are written to it and can then echo them back when + read. Example of a Sample Echo Pseudo-Device Driver for @@ -382,8 +381,7 @@ echo_write(struct cdev *dev __unused, st DEV_MODULE(echo,echo_loader,NULL);</programlisting> </example> - <para>With this driver loaded you should now be able to type - something like:</para> + <para>With this driver loaded try:</para> <screen>&prompt.root; <userinput>echo -n "Test Data" > /dev/echo</userinput> &prompt.root; <userinput>cat /dev/echo</userinput> From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 13:46:30 2013 Return-Path: <owner-svn-doc-all@FreeBSD.ORG> Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 11D1EB9D; Mon, 11 Feb 2013 13:46:30 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 56490DAA; Mon, 11 Feb 2013 13:46:29 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1BDkThC012901; Mon, 11 Feb 2013 13:46:29 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1BDkTJJ012899; Mon, 11 Feb 2013 13:46:29 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201302111346.r1BDkTJJ012899@svn.freebsd.org> From: Eitan Adler <eadler@FreeBSD.org> Date: Mon, 11 Feb 2013 13:46:29 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40943 - head/en_US.ISO8859-1/books/arch-handbook/driverbasics X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" <svn-doc-all.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-all> List-Post: <mailto:svn-doc-all@freebsd.org> List-Help: <mailto:svn-doc-all-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=subscribe> X-List-Received-Date: Mon, 11 Feb 2013 13:46:30 -0000 Author: eadler Date: Mon Feb 11 13:46:28 2013 New Revision: 40943 URL: http://svnweb.freebsd.org/changeset/doc/40943 Log: Fix indentation. Translators may probably ignore. Approved by: bcr (mentor) Modified: head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml Modified: head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml Mon Feb 11 13:46:26 2013 (r40942) +++ head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml Mon Feb 11 13:46:28 2013 (r40943) @@ -67,25 +67,30 @@ a running kernel without constantly rebooting to test changes.</para> - <indexterm><primary>kernel - modules</primary><secondary>loading</secondary></indexterm> + <indexterm> + <primary>kernel modules</primary> + <secondary>loading</secondary> + </indexterm> <indexterm><primary>kernel modules</primary><secondary>unloading</secondary></indexterm> <indexterm><primary>kernel modules</primary><secondary>listing</secondary></indexterm> <para>The kld interface is used through:</para> <itemizedlist> - <listitem><simpara><command>kldload</command> - loads a new kernel - module</simpara></listitem> - <listitem><simpara><command>kldunload</command> - unloads a kernel - module</simpara></listitem> - <listitem><simpara><command>kldstat</command> - lists the currently loaded - modules</simpara></listitem> + <listitem> + <simpara><command>kldload</command> - loads a new kernel + module</simpara></listitem> + <listitem> + <simpara><command>kldunload</command> - unloads a kernel + module</simpara></listitem> + <listitem> + <simpara><command>kldstat</command> - lists loaded + modules</simpara></listitem> </itemizedlist> <para>Skeleton Layout of a kernel module</para> -<programlisting>/* + <programlisting>/* * KLD Skeleton * Inspired by Andrew Reiter's Daemonnews article */ From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 13:46:31 2013 Return-Path: <owner-svn-doc-all@FreeBSD.ORG> Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 91336B9E; Mon, 11 Feb 2013 13:46:31 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 6B730DAB; Mon, 11 Feb 2013 13:46:31 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1BDkVKH012938; Mon, 11 Feb 2013 13:46:31 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1BDkVpm012937; Mon, 11 Feb 2013 13:46:31 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201302111346.r1BDkVpm012937@svn.freebsd.org> From: Eitan Adler <eadler@FreeBSD.org> Date: Mon, 11 Feb 2013 13:46:31 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40944 - head/en_US.ISO8859-1/books/arch-handbook/driverbasics X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" <svn-doc-all.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-all> List-Post: <mailto:svn-doc-all@freebsd.org> List-Help: <mailto:svn-doc-all-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=subscribe> X-List-Received-Date: Mon, 11 Feb 2013 13:46:31 -0000 Author: eadler Date: Mon Feb 11 13:46:30 2013 New Revision: 40944 URL: http://svnweb.freebsd.org/changeset/doc/40944 Log: Fix indentation and whitespace Translators may ignore Approved by: bcr (mentor) Modified: head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml Modified: head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml Mon Feb 11 13:46:28 2013 (r40943) +++ head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml Mon Feb 11 13:46:30 2013 (r40944) @@ -148,10 +148,10 @@ KMOD=skeleton .include <bsd.kmod.mk></programlisting> <para>Running <command>make</command> with this makefile - will create a file <filename>skeleton.ko</filename> that can - be loaded into the kernel by typing: -<screen>&prompt.root; <userinput>kldload -v ./skeleton.ko</userinput></screen> - </para> + will create a file <filename>skeleton.ko</filename> that can + be loaded into the kernel by typing:</para> + + <screen>&prompt.root; <userinput>kldload -v ./skeleton.ko</userinput></screen> </sect2> </sect1> @@ -164,8 +164,8 @@ KMOD=skeleton accesses a device node. The <command>/dev/MAKEDEV</command> script makes most of the device nodes for your system but if you are doing your own driver development it may be necessary to - create your own device nodes with <command>mknod</command>. - </para> + create your own device nodes with + <command>mknod</command>.</para> <sect2> <title>Creating Static Device Nodes @@ -422,8 +422,7 @@ Closing device "echo". (partition) to two devices with different semantics significantly complicated the relevant kernel code &os; dropped support for cached disk devices as part of the modernization of the disk I/O - infrastructure. - + infrastructure. From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 13:47:43 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C81122F3; Mon, 11 Feb 2013 13:47:43 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id AC9D9FB; Mon, 11 Feb 2013 13:47:43 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1BDlhfE013135; Mon, 11 Feb 2013 13:47:43 GMT (envelope-from linimon@svn.freebsd.org) Received: (from linimon@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1BDlh5b013134; Mon, 11 Feb 2013 13:47:43 GMT (envelope-from linimon@svn.freebsd.org) Message-Id: <201302111347.r1BDlh5b013134@svn.freebsd.org> From: Mark Linimon Date: Mon, 11 Feb 2013 13:47:43 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40945 - head/en_US.ISO8859-1/articles/portbuild X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 13:47:43 -0000 Author: linimon Date: Mon Feb 11 13:47:43 2013 New Revision: 40945 URL: http://svnweb.freebsd.org/changeset/doc/40945 Log: Move some variable definitions away from control of PORTBUILD_USER and into control of SRCBUILD_USER, from portbuild/conf/server.conf to portbuild/admin/conf/admin.conf, respectively. Implicitly requested by: rwatson Modified: head/en_US.ISO8859-1/articles/portbuild/article.xml Modified: head/en_US.ISO8859-1/articles/portbuild/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/portbuild/article.xml Mon Feb 11 13:46:30 2013 (r40944) +++ head/en_US.ISO8859-1/articles/portbuild/article.xml Mon Feb 11 13:47:43 2013 (r40945) @@ -2783,7 +2783,38 @@ sysutils/zfs-stats - (in process of being refactored) + Configure the server by making the following changes to + /a/portbuild/admin/conf/admin.conf: + + + + For each source branch you will be building for, set + SRC_BRANCHES and + SRC_BRANCH_branch_SUBDIR + as detailed in . + You should not need to change + SRC_BRANCHES_PATTERN. + + + + Set ZFS_VOLUME and + ZFS_MOUNTPOINT to whatever you + chose above. + + + + Set VCS_REPOSITORY to whatever + you chose above. + + + + Set MASTER_URL to the http + URL of your server. This will be stamped into the + package build logs and the indices thereof. + + + + Most of the other default values should be fine. @@ -2836,6 +2867,7 @@ sysutils/zfs-stats list of architectures you wish to build packages for. + Set UPLOAD_DIRECTORY, @@ -2858,6 +2891,7 @@ sysutils/zfs-stats for your site. + Most of the other default values should be fine. From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 14:50:33 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 901E528B; Mon, 11 Feb 2013 14:50:33 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 81E2F709; Mon, 11 Feb 2013 14:50:33 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1BEoXUt033683; Mon, 11 Feb 2013 14:50:33 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1BEoXIR033682; Mon, 11 Feb 2013 14:50:33 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201302111450.r1BEoXIR033682@svn.freebsd.org> From: Dru Lavigne Date: Mon, 11 Feb 2013 14:50:33 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40946 - head/en_US.ISO8859-1/books/handbook/geom X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 14:50:33 -0000 Author: dru Date: Mon Feb 11 14:50:33 2013 New Revision: 40946 URL: http://svnweb.freebsd.org/changeset/doc/40946 Log: This patch addresses the following: - fixes xref tags - some tightening and removing of redundancy - fixed some confusion in glabel section Approved by gjb (mentor) Modified: head/en_US.ISO8859-1/books/handbook/geom/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/geom/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/geom/chapter.xml Mon Feb 11 13:47:43 2013 (r40945) +++ head/en_US.ISO8859-1/books/handbook/geom/chapter.xml Mon Feb 11 14:50:33 2013 (r40946) @@ -35,11 +35,11 @@ control utilities which use the framework for configuration. This chapter will not go into in depth discussion on how GEOM handles or controls I/O, the underlying subsystem, or code. - This information is provided through the &man.geom.4; manual - page and its various SEE ALSO references. This chapter is also - not a definitive guide to RAID - configurations. Only GEOM-supported RAID - classifications will be discussed. + This information is provided in &man.geom.4; and its various + SEE ALSO references. This chapter is also + not a definitive guide to RAID configurations + and only GEOM-supported RAID classifications + will be discussed. After reading this chapter, you will know: @@ -70,13 +70,13 @@ - Understand how &os; treats disk devices - (). + Understand how &os; treats disk devices. - Know how to configure and install a new &os; kernel - (). + Know how to configure and install a new &os; kernel. @@ -84,12 +84,12 @@ GEOM Introduction - GEOM permits access and control to classes — Master - Boot Records, BSD labels, etc — through - the use of providers, or the special files in - /dev. Supporting various - software RAID configurations, GEOM will - transparently provide access to the operating system and + GEOM permits access and control to classes, such as Master + Boot Records and BSD labels, through the use + of providers, or the special files in /dev. By supporting various + software RAID configurations, GEOM + transparently provides access to the operating system and operating system utilities. @@ -117,13 +117,13 @@ Striping - Striping is a method used to combine several disk drives - into a single volume. In many cases, this is done through the - use of hardware controllers. The GEOM disk subsystem provides - software support for RAID0, also known as - disk striping. + Striping combine several disk drives into a single volume. + In many cases, this is done through the use of hardware + controllers. The GEOM disk subsystem provides software support + for RAID0, also known as disk + striping. - In a RAID0 system, data are split up in + In a RAID0 system, data is split into blocks that get written across all the drives in the array. Instead of having to wait on the system to write 256k to one disk, a RAID0 system can simultaneously write @@ -168,7 +168,7 @@ Determine the device names for the disks which will be striped, and create the new stripe device. For example, to stripe two unused and unpartitioned - ATA disks, for example + ATA disks with device names of /dev/ad2 and /dev/ad3: @@ -179,21 +179,21 @@ Done. - Write a standard label, also known as a partition - table, on the new volume and install the default - bootstrap code: + Write a standard label, also known as a partition table, + on the new volume and install the default bootstrap + code: &prompt.root; bsdlabel -wB /dev/stripe/st0 - This process should have created two other devices - in the /dev/stripe - directory in addition to the st0 - device. Those include st0a and - st0c. At this point a file system - may be created on the st0a device - with the newfs utility: + This process should create two other devices in + /dev/stripe in + addition to st0. Those include + st0a and + st0c. At this point, a file system + may be created on st0a using + newfs: &prompt.root; newfs -U /dev/stripe/st0a @@ -209,10 +209,9 @@ Done. To mount this striped file system automatically during the boot process, place the volume information in - /etc/fstab file. For this purpose, a - permanent mount point, named - stripe, is - created: + /etc/fstab. In this example, a + permanent mount point, named stripe, is created: &prompt.root; mkdir /stripe &prompt.root; echo "/dev/stripe/st0a /stripe ufs rw 2 2" \ @@ -249,8 +248,8 @@ Done. replace the failed drive without user interruption. Two common situations are illustrated in these examples. - The first is creating a mirror out of two new drives and using - it as a replacement for an existing single drive. The second + The first creates a mirror out of two new drives and uses it + as a replacement for an existing single drive. The second example creates a mirror on a single new drive, copies the old drive's data to it, then inserts the old drive into the mirror. While this procedure is slightly more complicated, it @@ -317,28 +316,28 @@ Done. used to replace the old single disk. &man.gmirror.8; requires a kernel module, - geom_mirror.ko, either built into the - kernel or loaded at boot- or run-time. Manually load the - kernel module now: + geom_mirror.ko, either compiled into a + custom kernel or loaded at boot- or run-time. To manually + load the kernel module now: &prompt.root; gmirror load - Create the mirror with the two new drives. + To create the mirror with the two new drives. &prompt.root; gmirror label -v gm0 /dev/ada1 /dev/ada2 gm0 is a user-chosen device name assigned to the new mirror. After the mirror has been - started, this device name will appear in the - /dev/mirror/ directory. + started, this device name will appear in + /dev/mirror/. MBR and bsdlabel partition tables can now be created on the mirror with &man.gpart.8;. Here we show a traditional split-filesystem layout, with partitions for /, swap, /var, /tmp, and /usr. A - single / filesystem and a swap partition - will also work. + single / and a swap partition will also + work. Partitions on the mirror do not have to be the same size as those on the existing disk, but they must be large enough @@ -384,8 +383,8 @@ Done. &prompt.root; newfs -U /dev/mirror/gm0s1e &prompt.root; newfs -U /dev/mirror/gm0s1f - Filesystems from the original disk - (ada0) can now be copied onto the + Filesystems from the original + ada0 disk can now be copied onto the mirror with &man.dump.8; and &man.restore.8;. &prompt.root; mount /dev/mirror/gm0s1a /mnt @@ -419,8 +418,8 @@ Done. are identical, it does not matter which is selected to boot. - See the - Troubleshooting + See the Troubleshooting section if there are problems booting. Powering down and disconnecting the original ada0 disk will allow it to be kept as an offline backup. @@ -432,23 +431,23 @@ Done. Creating a Mirror with an Existing Drive - In this example, &os; has already been installed on a - single disk, ada0. A new disk, + In this example, &os; has been installed on a single + disk, ada0. A new disk, ada1, has been connected to the system. A one-disk mirror will be created on the new disk, - the existing system copied onto it, and then the old disk will be - inserted into the mirror. This slightly complex procedure is - required because &man.gmirror.8; needs to put a 512-byte block - of metadata at the end of each disk, and the existing - ada0 has usually had all of its space + the existing system copied onto it, and then the old disk will + be inserted into the mirror. This slightly complex procedure + is required because &man.gmirror.8; needs to put a 512-byte + block of metadata at the end of each disk, and the existing + ada0 usually has all of its space already allocated. - Load the &man.gmirror.8; kernel module. + Load the &man.gmirror.8; kernel module: &prompt.root; gmirror load Check the media size of the original disk with - &man.diskinfo.8;. + &man.diskinfo.8;: &prompt.root; diskinfo -v ada0 | head -n3 /dev/ada0 @@ -461,11 +460,11 @@ Done. size. This drive does not store any data, but is used only to limit the size of the mirror. When &man.gmirror.8; creates the mirror, it will restrict the capacity to the size of - gzero.nop even if the new drive + gzero.nop, even if the new drive (ada1) has more space. Note that the 1000204821504 in the second line - should be equal to ada0's media size - as shown by &man.diskinfo.8; above. + should be equal to the size of ada0 + as shown by &man.diskinfo.8;. &prompt.root; geom zero load &prompt.root; gnop create -s 1000204821504 gzero @@ -502,7 +501,7 @@ Done. be explained later. In either case, partition tables on the primary disk - should be copied first. It can be done by using &man.gpart.8; + should be copied first using the &man.gpart.8; backup and restore subcommands. @@ -527,8 +526,8 @@ BSD 8 6 freebsd-ufs 130023424 838860800 7 freebsd-ufs 968884224 984640881 - If the whole disk was used in the output of &man.gpart.8; - show, the capacity in these partition + If the whole disk shows as used in the output of + gpart show, the capacity in these partition tables must be reduced by one sector. Edit the two files, reducing the size of both the slice and last partition by one. These are the last numbers in each listing. @@ -550,13 +549,13 @@ BSD 8 disk, these two files can be used without modification. Now restore the partition table into - mirror/gm0. + mirror/gm0: &prompt.root; gpart restore mirror/gm0 < table.ada0 &prompt.root; gpart restore mirror/gm0s1 < table.ada0s1 - Check the partition table with the &man.gpart.8; - show. This example has + Check the partition table with + gpart show. This example has gm0s1a for /, gm0s1d for /var, gm0s1e for /usr, @@ -707,8 +706,7 @@ mirror/gm0 COMPLETE ada1 (ACTIVE) BIOS settings may have to be changed to boot from one of the new mirrored drives. Either mirror drive can be - used for booting. As components of a mirror, they contain - identical data. + used for booting as they contain identical data. @@ -742,10 +740,10 @@ mountroot> Forgetting to load the geom_mirror module in /boot/loader.conf can cause this - problem. To fix it, boot from a &os;-9 or later CD or USB - stick and choose Shell at the first - prompt. Then load the mirror module and mount the mirror - device: + problem. To fix it, boot from a &os; 9.0 or later + installation media and choose Shell at + the first prompt. Then load the mirror module and mount + the mirror device: &prompt.root; gmirror load &prompt.root; mount /dev/mirror/gm0s1a /mnt @@ -759,14 +757,14 @@ mountroot> Other problems that cause error 19 require more effort to fix. Enter - ufs:/dev/ada0s1a at the prompt. - Although the system should boot from + ufs:/dev/ada0s1a at the boot loader + prompt. Although the system should boot from ada0, another prompt to select a shell appears because /etc/fstab is incorrect. Press the Enter key at the prompt. Undo the modifications so far by reverting /etc/fstab, mounting filesystems from - the original disk (ada0) instead + the original ada0 instead of the mirror. Reboot the system and try the procedure again. @@ -780,24 +778,20 @@ mountroot> Recovering from Disk Failure - The wonderful part about disk mirroring is that an - individual disk can fail without causing the mirror to lose - any data. - - ada0 is one of two drives making - up the mirror in the previous example. If - ada0 fails, the mirror will continue - to work, providing data from the remaining working drive, - ada1. - - To replace the failed drive, the computer is shut down and - the failed drive is physically replaced with a new drive of - equal or greater capacity. Manufacturers use somewhat - arbitrary values when rating drives in gigabytes, and the - only way to really be sure is to compare the total count of - sectors shown by diskinfo -v. A drive with - larger capacity than the mirror will work, although the extra - space on the new drive will not be used. + The benefit of disk mirroring is that an individual disk + can fail without causing the mirror to lose any data. In the + above example, if ada0 fails, the + mirror will continue to work, providing data from the + remaining working drive, ada1. + + To replace the failed drive, shut down the system and + physically replace the failed drive with a new drive of equal + or greater capacity. Manufacturers use somewhat arbitrary + values when rating drives in gigabytes, and the only way to + really be sure is to compare the total count of sectors shown + by diskinfo -v. A drive with larger + capacity than the mirror will work, although the extra space + on the new drive will not be used. After the computer is powered back up, the mirror will be running in a degraded mode with only one drive. @@ -866,18 +860,18 @@ mountroot> RAID3 is a method used to combine several - disk drives into a single volume with a dedicated parity - disk. In a RAID3 system, data is split up - into a number of bytes that are written across all the drives in - the array except for one disk which acts as a dedicated parity - disk. This means that reading 1024KB from a + disk drives into a single volume with a dedicated parity disk. + In a RAID3 system, data is split up into a + number of bytes that are written across all the drives in the + array except for one disk which acts as a dedicated parity disk. + This means that reading 1024KB from a RAID3 implementation will access all disks in - the array. Performance can be enhanced by using multiple - disk controllers. The RAID3 array provides a + the array. Performance can be enhanced by using multiple disk + controllers. The RAID3 array provides a fault tolerance of 1 drive, while providing a capacity of 1 - 1/n times the total capacity of all drives in the array, where n is the number of hard drives in the array. Such a configuration - is mostly suitable for storing data of larger sizes, e.g., + is mostly suitable for storing data of larger sizes such as multimedia files. At least 3 physical hard drives are required to build a @@ -885,7 +879,7 @@ mountroot> size, since I/O requests are interleaved to read or write to multiple disks in parallel. Also, due to the nature of RAID3, the number of drives must be - equal to 3, 5, 9, 17, etc. (2^n + 1). + equal to 3, 5, 9, 17, and so on, or 2^n + 1. Creating a Dedicated <acronym>RAID</acronym>3 @@ -955,11 +949,7 @@ Done.</screen> <para>Many numbers will glide across the screen, and after a bit of time, the process will be complete. The volume has - been created and is ready to be mounted.</para> - </step> - - <step> - <para>The last step is to mount the file system:</para> + been created and is ready to be mounted:</para> <screen>&prompt.root; <userinput>mount /dev/raid3/gr0p1 /multimedia/</userinput></screen> @@ -975,16 +965,16 @@ Done.</screen> <step> <para>The <filename>geom_raid3.ko</filename> module must be loaded before the array can be mounted. To automatically - load the kernel module during the system initialization, - add the following line to the - <filename>/boot/loader.conf</filename> file:</para> + load the kernel module during system initialization, add + the following line to + <filename>/boot/loader.conf</filename>:</para> <programlisting>geom_raid3_load="YES"</programlisting> </step> <step> - <para>The following volume information must be added to the - <filename>/etc/fstab</filename> file in order to + <para>The following volume information must be added to + <filename>/etc/fstab</filename> in order to automatically mount the array's file system during the system boot process:</para> @@ -998,7 +988,7 @@ Done.</screen> <title>GEOM Gate Network Devices GEOM supports the remote use of devices, such as disks, - CD-ROMs, files, etc. through the use of the gate utilities. + CD-ROMs, and files through the use of the gate utilities. This is similar to NFS. To begin, an exports file must be created. This file @@ -1010,8 +1000,8 @@ Done. 192.168.1.0/24 RW /dev/da0s4d - It will allow all hosts inside the private network access - the file system on the da0s4d + This allows all hosts inside the specified private network + access to the file system on the da0s4d partition. To export this device, ensure it is not currently mounted, @@ -1019,25 +1009,24 @@ Done. &prompt.root; ggated - Now to mount the device on the client + To mount the device on the client machine, issue the following commands: &prompt.root; ggatec create -o rw 192.168.1.1 /dev/da0s4d ggate0 &prompt.root; mount /dev/ggate0 /mnt - From here on, the device may be accessed through the - /mnt mount point. + The device may now be accessed through the /mnt mount point. - It should be pointed out that this will fail if the device - is currently mounted on either the server machine or any other - machine on the network. + However, this will fail if the device is currently mounted + on either the server machine or any other machine on the + network. - When the device is no longer needed, it may be safely - unmounted with the &man.umount.8; command, similar to any other - disk device. + When the device is no longer needed, unmount it with + &man.umount.8;, similar to any other disk device. @@ -1050,34 +1039,32 @@ ggate0 Disk Labels - During system initialization, the &os; kernel will create + During system initialization, the &os; kernel creates device nodes as devices are found. This method of probing for - devices raises some issues, for instance what if a new disk - device is added via USB? It is very likely - that a flash device may be handed the device name of + devices raises some issues. For instance, what if a new disk + device is added via USB? It is likely that + a flash device may be handed the device name of da0 and the original da0 shifted to da1. This will cause issues mounting file systems if they are listed in - /etc/fstab, effectively, this may also - prevent the system from booting. + /etc/fstab which may also prevent the + system from booting. - One solution to this issue is to chain the - SCSI devices in order so a new device added - to the SCSI card will be issued unused device - numbers. But what about USB devices which - may replace the primary SCSI disk? This - happens because USB devices are usually - probed before the SCSI card. One solution is - to only insert these devices after the system has been booted. - Another method could be to use only a single - ATA drive and never list the - SCSI devices in + One solution is to chain SCSI devices + in order so a new device added to the SCSI + card will be issued unused device numbers. But what about + USB devices which may replace the primary + SCSI disk? This happens because + USB devices are usually probed before the + SCSI card. One solution is to only insert + these devices after the system has been booted. Another method + is to use only a single ATA drive and never + list the SCSI devices in /etc/fstab. - A better solution is available. By using the - glabel utility, an administrator or user may - label their disk devices and use these labels in + A better solution is to use glabel to + label the disk devices and use the labels in /etc/fstab. Because glabel stores the label in the last sector of a given provider, the label will remain persistent across @@ -1086,39 +1073,33 @@ ggate0 through. - This goes without saying that a label be permanent. The - glabel utility may be used to create both a - transient and permanent label. Only the permanent label will - remain consistent across reboots. See the &man.glabel.8; - manual page for more information on the differences between - labels. + glabel can create both transient and + permanent labels. Only permanent labels are consistent across + reboots. Refer to &man.glabel.8; for more information on the + differences between labels. Label Types and Examples - There are two types of labels, a generic label and a - file system label. Labels can be permanent or temporary. - Permanent labels can be created with the &man.tunefs.8; - or &man.newfs.8; commands. They will then be created - in a sub-directory of - /dev, which will be - named according to their file system type. For example, + Permanent labels can be a generic or a file system label. + Permanent file system labels can be created with + &man.tunefs.8; or &man.newfs.8;. These types of labels are + created in a sub-directory of /dev, and will be named + according to the file system type. For example, UFS2 file system labels will be created in - the /dev/ufs directory. - Permanent labels can also be created with the glabel - label command. These are not file system specific, - and will be created in the - /dev/label - directory. - - A temporary label will go away with the next reboot. - These labels will be created in the - /dev/label directory - and are perfect for experimentation. A temporary label can be - created using the glabel create command. - For more information, please read the manual page of - &man.glabel.8;. + /dev/ufs. Generic + permanent labels can be created with glabel + label. These are not file system specific and + will be created in /dev/label. + + Temporary labels are destroyed at the next reboot. These + labels are created in /dev/label and are suited to + experimentation. A temporary label can be created using + glabel create. @@ -1131,14 +1112,12 @@ ggate0 If the file system is full, this may cause data - corruption; however, if the file system is full then the - main goal should be removing stale files and not adding - labels. + corruption. - A label should now exist in - /dev/ufs which may be - added to /etc/fstab: + A label should now exist in /dev/ufs which may be added + to /etc/fstab: /dev/ufs/home /home ufs rw 2 2 @@ -1147,7 +1126,7 @@ ggate0 to run tunefs. - Now the file system may be mounted like normal: + Now the file system may be mounted: &prompt.root; mount /home @@ -1160,8 +1139,8 @@ ggate0 File systems may also be created with a default label by using the flag with - newfs. See the &man.newfs.8; manual page - for more information. + newfs. Refer to &man.newfs.8; for + more information. The following command can be used to destroy the label: @@ -1185,7 +1164,7 @@ ggate0 /, /var, /usr and - /tmp file systems, as + /tmp, as well as a swap partition. Reboot the system, and at the &man.loader.8; prompt, @@ -1207,8 +1186,8 @@ GEOM_LABEL: Label for provider /dev/ad0s The system will continue with multi-user boot. After the boot completes, edit /etc/fstab and replace the conventional device names, with their respective - labels. The final /etc/fstab file will - look like the following: + labels. The final /etc/fstab will + look like this: # Device Mountpoint FStype Options Dump Pass# /dev/label/swap none swap sw 0 0 @@ -1232,24 +1211,23 @@ devfs on /dev (devfs, local) Starting with &os; 7.2, the &man.glabel.8; class supports a new label type for UFS file systems, based on the unique file system id, - ufsid. These labels may be found in the - /dev/ufsid directory - and are created automatically during system startup. It is - possible to use ufsid labels to mount - partitions using the /etc/fstab facility. - Use the glabel status command to receive a - list of file systems and their corresponding - ufsid labels: + ufsid. These labels may be found in + /dev/ufsid and are + created automatically during system startup. It is possible + to use ufsid labels to mount partitions + using /etc/fstab. Use glabel + status to receive a list of file systems and their + corresponding ufsid labels: &prompt.user; glabel status Name Status Components ufsid/486b6fc38d330916 N/A ad4s1d ufsid/486b6fc16926168e N/A ad4s1f - In the above example ad4s1d - represents the /var - file system, while ad4s1f represents - the /usr file system. + In the above example, ad4s1d + represents /var, + while ad4s1f represents + /usr. Using the ufsid values shown, these partitions may now be mounted with the following entries in /etc/fstab: @@ -1258,9 +1236,9 @@ ufsid/486b6fc16926168e N/A ad4s1f Any partitions with ufsid labels can be - mounted in this way, eliminating the need to create permanent - labels for them manually, while still enjoying the benefits of - device-name independent mounting. + mounted in this way, eliminating the need to manually create + permanent labels, while still enjoying the benefits of device + name independent mounting. @@ -1274,51 +1252,50 @@ ufsid/486b6fc16926168e N/A ad4s1fJournaling - With the release of &os; 7.0, the long awaited feature - of journals has been implemented. The implementation itself is - provided through the GEOM subsystem and is - easily configured via the &man.gjournal.8; utility. - - What is journaling? Journaling capability stores a log of - file system transactions, i.e.: changes that make up a complete - disk write operation, before meta-data and file writes are - committed to the disk proper. This transaction log can later - be replayed to redo file system transactions, preventing file - system inconsistencies. - - This method is yet another mechanism to protect against data - loss and inconsistencies of the file system. Unlike Soft - Updates which tracks and enforces meta-data updates and - Snapshots which is an image of the file system, an actual log is - stored in disk space specifically reserved for this task, and in - some cases may be stored on another disk entirely. + Beginning with &os; 7.0, support for UFS journals is + available. The implementation is provided through the + GEOM subsystem and is configured using + &man.gjournal.8;. + + Journaling stores a log of file system transactions, such as + changes that make up a complete disk write operation, before + meta-data and file writes are committed to the disk. This + transaction log can later be replayed to redo file system + transactions, preventing file system inconsistencies. + + This method provides another mechanism to protect against + data loss and inconsistencies of the file system. Unlike Soft + Updates, which tracks and enforces meta-data updates, and + snapshots, which create an image of the file system, a log is + stored in disk space specifically for this task, and in + some cases, may be stored on another disk entirely. Unlike other file system journaling implementations, the gjournal method is block based and not - implemented as part of the file system - only as a + implemented as part of the file system. It is a GEOM extension. To enable support for gjournal, the - &os; kernel must have the following option - which is the - default on &os; 7.0 and later systems: + &os; kernel must have the following option which is the + default on &os; 7.0 and later: options UFS_GJOURNAL If journaled volumes need to be mounted during startup, the - geom_journal.ko kernel module will also - have to be loaded, by adding the following line in + geom_journal.ko kernel module needs to be + loaded, by adding the following line to /boot/loader.conf: geom_journal_load="YES" - Alternatively, this function can also be built into a custom + Alternatively, this function can be built into a custom kernel, by adding the following line in the kernel configuration file: options GEOM_JOURNAL Creating a journal on a free file system may now be done - using the following steps, considering that the + using the following steps. In this example, da4 is a new SCSI disk: @@ -1332,12 +1309,11 @@ ufsid/486b6fc16926168e N/A ad4s1f&prompt.root; newfs -O 2 -J /dev/da4.journal - The previously issued command will create a - UFS2 file system on the journaled - device. + This command will creates a UFS2 file + system on the journaled device. - Effectively mount the device at the - desired point with: + mount the device at the desired point + with: &prompt.root; mount /dev/da4.journal /mnt @@ -1351,21 +1327,21 @@ ufsid/486b6fc16926168e N/A ad4s1fad4s2.journal. - For better performance, keeping the journal on another disk - may be desired. For these cases, the journal provider or - storage device should be listed after the device to enable - journaling on. Journaling may also be enabled on current file - systems by using tunefs; however, always make - a backup before attempting to alter a file system. In most - cases, the gjournal will fail if it is unable - to create the actual journal but this does not protect against - data loss incurred as a result of misusing + For better performance, the journal may be kept on another + disk. In this configuration, the journal provider or storage + device should be listed after the device to enable journaling + on. Journaling may also be enabled on current file systems by + using tunefs. However, + always make a backup before attempting to + alter a file system. In most cases, gjournal + will fail if it is unable to create the journal, but this does + not protect against data loss incurred as a result of misusing tunefs. It is also possible to journal the boot disk of a &os; - system. Please refer to the article Implementing UFS - Journaling on a Desktop PC for detailed instructions - on this task. + Journaling on a Desktop PC for detailed + instructions. From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 14:58:34 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A3ABE532; Mon, 11 Feb 2013 14:58:34 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 93815782; Mon, 11 Feb 2013 14:58:34 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1BEwY3k034822; Mon, 11 Feb 2013 14:58:34 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1BEwYW7034821; Mon, 11 Feb 2013 14:58:34 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201302111458.r1BEwYW7034821@svn.freebsd.org> From: Dru Lavigne Date: Mon, 11 Feb 2013 14:58:34 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40947 - head/en_US.ISO8859-1/books/handbook/filesystems X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 14:58:34 -0000 Author: dru Date: Mon Feb 11 14:58:34 2013 New Revision: 40947 URL: http://svnweb.freebsd.org/changeset/doc/40947 Log: This patch addresses the following: - removes you - fixes xref - modernizes the intro - modernizes the ZFS RAM section - updates the date in one sample output Approved by: gjb (mentor) Modified: head/en_US.ISO8859-1/books/handbook/filesystems/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/filesystems/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/filesystems/chapter.xml Mon Feb 11 14:50:33 2013 (r40946) +++ head/en_US.ISO8859-1/books/handbook/filesystems/chapter.xml Mon Feb 11 14:58:34 2013 (r40947) @@ -27,32 +27,30 @@ File systems are an integral part of any operating system. - They allow for users to upload and store files, provide access - to data, and of course, make hard drives useful. Different - operating systems usually have one major aspect in common, that - is their native file system. On &os; this file system is known - as the Fast File System or FFS which is built - on the original Unix™ File System, also known as - UFS. This is the native file system on &os; - which is placed on hard disks for access to data. - - &os; also supports a multitude of different file systems to - provide support for accessing data from other operating systems - locally, i.e., data stored on locally attached - USB storage devices, flash drives, and hard - disks. There is also support for some non-native file systems. - These are file systems developed on other - operating systems, like the &linux; Extended File System - (EXT), and the &sun; Z File System - (ZFS). - - There are different levels of support for the various file - systems in &os;. Some will require a kernel module to be - loaded, others may require a toolset to be installed. This - chapter is designed to help users of &os; access other file - systems on their systems, starting with the &sun; Z file + They allow users to upload and store files, provide access + to data, and make hard drives useful. Different operating + systems differ in their native file system. Traditionally, the + native &os; file system has been the Unix File System + UFS which has been recently modernized as + UFS2. Since &os; 7.0, the Z File + System ZFS is also available as a native file system. + In addition to its native file systems, &os; supports a + multitude of other file systems so that data from other + operating systems can be accessed locally, such as data stored + on locally attached USB storage devices, + flash drives, and hard disks. This includes support for the + &linux; Extended File System (EXT) and the + µsoft; New Technology File System + (NTFS). + + There are different levels of &os; support for the various + file systems. Some require a kernel module to be loaded and + others may require a toolset to be installed. Some non-native + file system support is full read-write while others are + read-only. + After reading this chapter, you will know: @@ -62,11 +60,11 @@ - What file systems are supported by &os;. + Which file systems are supported by &os;. - How to enable, configure, access and make use of + How to enable, configure, access, and make use of non-native file systems. @@ -75,24 +73,25 @@ - Understand &unix; and &os; basics - (). + Understand &unix; and &os; basics. - Be familiar with - the basics of kernel configuration/compilation - (). + Be familiar with the basics of kernel configuration and + compilation. - Feel comfortable installing third party software - in &os; (). + Feel comfortable installing + software in &os;. - Have some familiarity with disks, storage and - device names in &os; (). + Have some familiarity with disks, storage, and device names in + &os;. @@ -100,73 +99,67 @@ The Z File System (ZFS) - The Z file system, developed by &sun;, is a new - technology designed to use a pooled storage method. This means - that space is only used as it is needed for data storage. It - has also been designed for maximum data integrity, supporting - data snapshots, multiple copies, and data checksums. A new - data replication model, known as RAID-Z has - been added. The RAID-Z model is similar - to RAID5 but is designed to prevent data - write corruption. + The Z file system, originally developed by &sun;, + is designed to use a pooled storage method in that space is only + used as it is needed for data storage. It is also designed for + maximum data integrity, supporting data snapshots, multiple + copies, and data checksums. It uses a software data replication + model, known as RAID-Z. + RAID-Z provides redundancy similar to + hardware RAID, but is designed to prevent + data write corruption and to overcome some of the limitations + of hardware RAID. ZFS Tuning - The ZFS subsystem utilizes much of - the system resources, so some tuning may be required to - provide maximum efficiency during every-day use. As an - experimental feature in &os; this may change in the near - future; however, at this time, the following steps are - recommended. + Some of the features provided by ZFS + are RAM-intensive, so some tuning may be required to provide + maximum efficiency on systems with limited RAM. Memory - The total system memory should be at least one gigabyte, - with two gigabytes or more recommended. In all of the - examples here, the system has one gigabyte of memory with - several other tuning mechanisms in place. - - Some people have had luck using fewer than one gigabyte - of memory, but with such a limited amount of physical - memory, when the system is under heavy load, it is very - plausible that &os; will panic due to memory - exhaustion. + At a bare minimum, the total system memory should be at + least one gigabyte. The amount of recommended RAM depends + upon the size of the pool and the ZFS features which are + used. A general rule of thumb is 1GB of RAM for every 1TB + of storage. If the deduplication feature is used, a general + rule of thumb is 5GB of RAM per TB of storage to be + deduplicated. While some users successfully use ZFS with + less RAM, it is possible that when the system is under heavy + load, it may panic due to memory exhaustion. Further tuning + may be required for systems with less than the recommended + RAM requirements. Kernel Configuration - It is recommended that unused drivers and options - be removed from the kernel configuration file. Since most - devices are available as modules, they may be loaded - using the /boot/loader.conf - file. - - Users of the &i386; architecture should add the - following option to their kernel configuration file, - rebuild their kernel, and reboot: + Due to the RAM limitations of the &i386; platform, users + using ZFS on the &i386; architecture should add the + following option to a custom kernel configuration file, + rebuild the kernel, and reboot: options KVA_PAGES=512 - This option will expand the kernel address space, thus - allowing the vm.kvm_size tunable to be - pushed beyond the currently imposed limit of 1 GB - (2 GB for PAE). To find the most - suitable value for this option, divide the desired address - space in megabytes by four (4). In this case, it is - 512 for 2 GB. + This option expands the kernel address space, allowing + the vm.kvm_size tunable to be pushed + beyond the currently imposed limit of 1 GB, or the + limit of 2 GB for PAE. To find the + most suitable value for this option, divide the desired + address space in megabytes by four (4). In this example, it + is 512 for 2 GB. Loader Tunables - The kmem address space should - be increased on all &os; architectures. On the test system + The kmem address space can + be increased on all &os; architectures. On a test system with one gigabyte of physical memory, success was achieved - with the following options which should be placed in the - /boot/loader.conf file and the system + with the following options added to + /boot/loader.conf, and the system restarted: vm.kmem_size="330M" @@ -191,22 +184,21 @@ vfs.zfs.vdev.cache.size="5M"&prompt.root; echo 'zfs_enable="YES"' >> /etc/rc.conf &prompt.root; service zfs start - The remainder of this document assumes three - SCSI disks are available, and their - device names are + The examples in this section assume three + SCSI disks with the device names da0, - da1 + da1, and da2. - Users of IDE hardware may use the + Users of IDE hardware should instead use ad - devices in place of SCSI hardware. + device names. Single Disk Pool To create a simple, non-redundant ZFS - pool using a single disk device, use the - zpool command: + pool using a single disk device, use + zpool: &prompt.root; zpool create example /dev/da0 @@ -220,12 +212,11 @@ devfs 1 1 0 /dev/ad0s1d 54098308 1032846 48737598 2% /usr example 17547136 0 17547136 0% /example - This output clearly shows the example - pool has not only been created but - mounted as well. It is also accessible - just like a normal file system, files may be created on it - and users are able to browse it as in the - following example: + This output shows that the example + pool has been created and mounted. It + is now accessible as a file system. Files may be created + on it and users can browse it, as seen in the following + example: &prompt.root; cd /example &prompt.root; ls @@ -236,25 +227,24 @@ drwxr-xr-x 2 root wheel 3 Aug 29 2 drwxr-xr-x 21 root wheel 512 Aug 29 23:12 .. -rw-r--r-- 1 root wheel 0 Aug 29 23:15 testfile - Unfortunately this pool is not taking advantage of - any ZFS features. Create a file system - on this pool, and enable compression on it: + However, this pool is not taking advantage of any + ZFS features. To create a dataset on + this pool with compression enabled: &prompt.root; zfs create example/compressed &prompt.root; zfs set compression=gzip example/compressed - The example/compressed is now a - ZFS compressed file system. Try copying - some large files to it by copying them to The example/compressed dataset is now + a ZFS compressed file system. Try + copying some large files to /example/compressed. - The compression may now be disabled with: + Compression can be disabled with: &prompt.root; zfs set compression=off example/compressed - To unmount the file system, issue the following command - and then verify by using the df - utility: + To unmount a file system, issue the following command + and then verify by using df: &prompt.root; zfs umount example/compressed &prompt.root; df @@ -264,7 +254,7 @@ devfs 1 1 0 /dev/ad0s1d 54098308 1032864 48737580 2% /usr example 17547008 0 17547008 0% /example - Re-mount the file system to make it accessible + To re-mount the file system to make it accessible again, and verify with df: &prompt.root; zfs mount example/compressed @@ -287,18 +277,19 @@ example on /example (zfs, local) example/data on /example/data (zfs, local) example/compressed on /example/compressed (zfs, local) - As observed, ZFS file systems, after - creation, may be used like ordinary file systems; however, - many other features are also available. In the following - example, a new file system, data is - created. Important files will be stored here, so the file - system is set to keep two copies of each data block: + ZFS datasets, after creation, may be + used like any file systems. However, many other features + are available which can be set on a per-dataset basis. In + the following example, a new file system, + data is created. Important files will be + stored here, the file system is set to keep two copies of + each data block: &prompt.root; zfs create example/data &prompt.root; zfs set copies=2 example/data It is now possible to see the data and space utilization - by issuing df again: + by issuing df: &prompt.root; df Filesystem 1K-blocks Used Avail Capacity Mounted on @@ -311,64 +302,56 @@ example/data 17547008 0 175 Notice that each file system on the pool has the same amount of available space. This is the reason for using - df through these examples, to show - that the file systems are using only the amount of space - they need and will all draw from the same pool. The - ZFS file system does away with concepts - such as volumes and partitions, and allows for several file - systems to occupy the same pool. Destroy the file systems, - and then destroy the pool as they are no longer - needed: + df in these examples, to show that the + file systems use only the amount of space they need and all + draw from the same pool. The ZFS file + system does away with concepts such as volumes and + partitions, and allows for several file systems to occupy + the same pool. + + To destroy the file systems and then destroy the pool as + they are no longer needed: &prompt.root; zfs destroy example/compressed &prompt.root; zfs destroy example/data &prompt.root; zpool destroy example - Disks go bad and fail, an unavoidable trait. When - this disk goes bad, the data will be lost. One method of - avoiding data loss due to a failed hard disk is to implement - a RAID. ZFS supports - this feature in its pool design which is covered in - the next section. <acronym>ZFS</acronym> RAID-Z - As previously noted, this section will assume that - three SCSI disks exist as devices - da0, da1 - and da2 (or - ad0 and beyond in case IDE disks - are being used). To create a RAID-Z - pool, issue the following command: + There is no way to prevent a disk from failing. One + method of avoiding data loss due to a failed hard disk is to + implement RAID. ZFS + supports this feature in its pool design. + + To create a RAID-Z pool, issue the + following command and specify the disks to add to the + pool: &prompt.root; zpool create storage raidz da0 da1 da2 - &sun; recommends that the amount of devices used - in a RAID-Z configuration is between - three and nine. If your needs call for a single pool to - consist of 10 disks or more, consider breaking it up into - smaller RAID-Z groups. If you only - have two disks and still require redundancy, consider - using a ZFS mirror instead. See the - &man.zpool.8; manual page for more details. + &sun; recommends that the amount of devices used in + a RAID-Z configuration is between + three and nine. For environments requiring a single pool + consisting of 10 disks or more, consider breaking it up + into smaller RAID-Z groups. If only + two disks are available and redundancy is a requirement, + consider using a ZFS mirror. Refer to + &man.zpool.8; for more details. - The storage zpool should have been - created. This may be verified by using the &man.mount.8; - and &man.df.1; commands as before. More disk devices may - have been allocated by adding them to the end of the list - above. Make a new file system in the pool, called - home, where user files will eventually - be placed: + This command creates the storage + zpool. This may be verified using &man.mount.8; and + &man.df.1;. This command makes a new file system in the + pool called home: &prompt.root; zfs create storage/home It is now possible to enable compression and keep extra - copies of the user's home directories and files. This may - be accomplished just as before using the following + copies of directories and files using the following commands: &prompt.root; zfs set copies=2 storage/home @@ -384,9 +367,9 @@ example/data 17547008 0 175 &prompt.root; ln -s /storage/home /usr/home Users should now have their data stored on the freshly - created /storage/home - file system. Test by adding a new user and logging in as - that user. + created /storage/home. Test by + adding a new user and logging in as that user. Try creating a snapshot which may be rolled back later: @@ -405,28 +388,27 @@ example/data 17547008 0 175 ls in the file system's .zfs/snapshot directory. For example, to see the previously taken - snapshot, perform the following command: + snapshot: &prompt.root; ls /storage/home/.zfs/snapshot - It is possible to write a script to perform monthly - snapshots on user data; however, over time, snapshots + It is possible to write a script to perform regular + snapshots on user data. However, over time, snapshots may consume a great deal of disk space. The previous snapshot may be removed using the following command: &prompt.root; zfs destroy storage/home@08-30-08 - After all of this testing, there is no reason we should - keep /storage/home - around in its present state. Make it the real - /home file - system: + After testing, /storage/home can be made the + real /home using + this command: &prompt.root; zfs set mountpoint=/home storage/home - Issuing the df and - mount commands will show that the system - now treats our file system as the real + Run df and + mount to confirm that the system now + treats the file system as the real /home: &prompt.root; mount @@ -455,8 +437,7 @@ storage/home 26320512 0 26320512 Recovering <acronym>RAID</acronym>-Z Every software RAID has a method of - monitoring their state. - ZFS is no exception. The status of + monitoring its state. The status of RAID-Z devices may be viewed with the following command: @@ -468,7 +449,7 @@ storage/home 26320512 0 26320512 all pools are healthy If there is an issue, perhaps a disk has gone offline, - the pool state will be returned and look similar to: + the pool state will look similar to: pool: storage state: DEGRADED @@ -489,14 +470,13 @@ config: errors: No known data errors - This states that the device was taken offline by the - administrator. This is true for this particular example. - To take the disk offline, the following command was - used: + This indicates that the device was previously taken + offline by the administrator using the following + command: &prompt.root; zpool offline storage da1 - It is now possible to replace the + It is now possible to replace da1 after the system has been powered down. When the system is back online, the following command may issued to replace the disk: @@ -529,37 +509,34 @@ errors: No known data errors Data Verification - As previously mentioned, ZFS uses + ZFS uses checksums to verify the integrity of - stored data. They are enabled automatically upon creation + stored data. These are enabled automatically upon creation of file systems and may be disabled using the following command: &prompt.root; zfs set checksum=off storage/home - This is not a wise idea, however, as checksums take - very little storage space and are more useful when enabled. - There also appears to be no noticeable costs in having them - enabled. While enabled, it is possible to have - ZFS check data integrity using checksum - verification. This process is known as - scrubbing. To verify the data integrity of - the storage pool, issue the following - command: + Doing so is not recommended as + checksums take very little storage space and are used to + check data integrity using checksum verification in a + process is known as scrubbing. To verify the + data integrity of the storage pool, issue + this command: &prompt.root; zpool scrub storage This process may take considerable time depending on the amount of data stored. It is also very - I/O intensive, so much that only one - of these operations may be run at any given time. After - the scrub has completed, the status is updated and may be - viewed by issuing a status request: + I/O intensive, so much so that only one + scrub may be run at any given time. After the scrub has + completed, the status is updated and may be viewed by + issuing a status request: &prompt.root; zpool status storage pool: storage state: ONLINE - scrub: scrub completed with 0 errors on Sat Aug 30 19:57:37 2008 + scrub: scrub completed with 0 errors on Sat Jan 26 19:57:37 2013 config: NAME STATE READ WRITE CKSUM @@ -571,43 +548,39 @@ config: errors: No known data errors - The completion time is in plain view in this example. - This feature helps to ensure data integrity over a long - period of time. - - There are many more options for the Z file system, - see the &man.zfs.8; and &man.zpool.8; manual - pages. + The completion time is displayed and helps to ensure + data integrity over a long period of time. + + Refer to &man.zfs.8; and &man.zpool.8; for other + ZFS options. ZFS Quotas - ZFS supports different types of quotas; the - refquota, the general quota, the user quota, and - the group quota. This section will explain the - basics of each one, and include some usage - instructions. - - Quotas limit the amount of space that a dataset - and its descendants can consume, and enforce a limit - on the amount of space used by filesystems and - snapshots for the descendants. In terms of users, - quotas are useful to limit the amount of space a - particular user can use. + ZFS supports different types of quotas: the refquota, + the general quota, the user quota, and the group quota. + This section explains the basics of each type and includes + some usage instructions. + + Quotas limit the amount of space that a dataset and its + descendants can consume, and enforce a limit on the amount + of space used by filesystems and snapshots for the + descendants. Quotas are useful to limit the amount of space + a particular user can use. Quotas cannot be set on volumes, as the - volsize property acts as an - implicit quota. + volsize property acts as an implicit + quota. - The refquota, - refquota=size, - limits the amount of space a dataset can consume - by enforcing a hard limit on the space used. However, - this hard limit does not include space used by descendants, - such as file systems or snapshots. + The + refquota=size + limits the amount of space a dataset can consume by + enforcing a hard limit on the space used. However, this + hard limit does not include space used by descendants, such + as file systems or snapshots. To enforce a general quota of 10 GB for storage/home/bob, use the @@ -615,9 +588,8 @@ errors: No known data errors &prompt.root; zfs set quota=10G storage/home/bob - User quotas limit the amount of space that can - be used by the specified user. The general format - is + User quotas limit the amount of space that can be used + by the specified user. The general format is userquota@user=size, and the user's name must be in one of the following formats: @@ -626,28 +598,28 @@ errors: No known data errors POSIX compatible name - (e.g., joe). + Interface">POSIX compatible name such as + joe. POSIX - numeric ID (e.g., - 789). + numeric ID such as + 789. SID name - (e.g., - joe.bloggs@example.com). + such as + joe.bloggs@example.com. SID - numeric ID (e.g., - S-1-123-456-789). + numeric ID such as + S-1-123-456-789. @@ -670,7 +642,7 @@ errors: No known data errors privilege are able to view and set everyone's quota. The group quota limits the amount of space that a - specified user group can consume. The general format is + specified group can consume. The general format is groupquota@group=size. To set the quota for the group @@ -680,30 +652,29 @@ errors: No known data errors &prompt.root; zfs set groupquota@firstgroup=50G To remove the quota for the group - firstgroup, or make sure that one - is not set, instead use: + firstgroup, or to make sure that + one is not set, instead use: &prompt.root; zfs set groupquota@firstgroup=none As with the user quota property, non-root users can only see the quotas - associated with the user groups that they belong to, however - a root user or a user with the + associated with the groups that they belong to. However, + root or a user with the groupquota privilege can view and set all quotas for all groups. - The zfs userspace subcommand displays - the amount of space consumed by each user on the specified - filesystem or snapshot, along with any specified quotas. - The zfs groupspace subcommand does the - same for groups. For more information about supported - options, or only displaying specific options, see - &man.zfs.1;. - - To list the quota for - storage/home/bob, if you have the - correct privileges or are root, use the - following: + To display the amount of space consumed by each user on + the specified filesystem or snapshot, along with any + specified quotas, use zfs userspace. + For group information, use zfs + groupspace. For more information about + supported options or how to display only specific options, + refer to &man.zfs.1;. + + Users with sufficient privileges and + root can list the quota for + storage/home/bob using: &prompt.root; zfs get quota storage/home/bob @@ -711,9 +682,9 @@ errors: No known data errors ZFS Reservations - ZFS supports two types of space reservations. - This section will explain the basics of each one, - and include some usage instructions. + ZFS supports two types of space reservations. This + section explains the basics of each and includes some usage + instructions. The reservation property makes it possible to reserve a minimum amount of space guaranteed @@ -732,23 +703,22 @@ errors: No known data errors not counted by the refreservation amount and so do not encroach on the space set. - Reservations of any sort are useful in many - situations, for example planning and testing the - suitability of disk space allocation in a new system, or - ensuring that enough space is available on file systems - for system recovery procedures and files. + Reservations of any sort are useful in many situations, + such as planning and testing the suitability of disk space + allocation in a new system, or ensuring that enough space is + available on file systems for system recovery procedures and + files. The general format of the reservation property is -reservation=size, + reservation=size, so to set a reservation of 10 GB on - storage/home/bobthe below command is - used: + storage/home/bob, use: &prompt.root; zfs set reservation=10G storage/home/bob To make sure that no reservation is set, or to remove a - reservation, instead use: + reservation, use: &prompt.root; zfs set reservation=none storage/home/bob @@ -770,24 +740,24 @@ errors: No known data errors &linux; Filesystems - This section will describe some of the &linux; filesystems + This section describes some of the &linux; filesystems supported by &os;. - Ext2FS + <acronym>ext2</acronym> - The &man.ext2fs.5; file system kernel implementation was - written by Godmar Back, and the driver first appeared in - &os; 2.2. In &os; 8 and earlier, the code is licensed under - the GNU Public License, however under &os; - 9, the code has been rewritten and it is now licensed under - the BSD license. - - The &man.ext2fs.5; driver will allow the &os; kernel - to both read and write to ext2 file - systems. + The &man.ext2fs.5; file system kernel implementation has + been available since &os; 2.2. In &os; 8.x and + earlier, the code is licensed under the + GPL. Since &os; 9.0, the code has + been rewritten and is now BSD + licensed. - First, load the kernel loadable module: + The &man.ext2fs.5; driver allows the &os; kernel to both + read and write to ext2 file systems. + + To access an ext2 file system, first + load the kernel loadable module: &prompt.root; kldload ext2fs @@ -800,11 +770,10 @@ errors: No known data errors XFS - The X file system, XFS, was originally - written by SGI for the - IRIX operating system, and they ported it - to &linux;. The source code has been released under the - GNU Public License. See + XFS was originally written by + SGI for the IRIX + operating system and was then ported to &linux; and + released under the GPL. See this page for more details. The &os; port was started by Russel Cattelan, &a.kan;, and &a.rodrigc;. @@ -814,21 +783,19 @@ errors: No known data errors &prompt.root; kldload xfs - The &man.xfs.5; driver lets the &os; kernel access - XFS filesystems. However, at present only read-only - access is supported. Writing to a volume is not - possible. + The &man.xfs.5; driver lets the &os; kernel access XFS + filesystems. However, only read-only access is supported and + writing to a volume is not possible. To mount a &man.xfs.5; volume located on - /dev/ad1s1, do the following: + /dev/ad1s1: &prompt.root; mount -t xfs /dev/ad1s1 /mnt - Also useful to note is that the - sysutils/xfsprogs port - contains the mkfs.xfs utility which enables - creation of XFS filesystems, plus utilities - for analysing and repairing them. + The sysutils/xfsprogs + port includes the mkfs.xfs which enables + the creation of XFS filesystems, plus + utilities for analyzing and repairing them. The -p flag to mkfs.xfs can be used to create an @@ -842,11 +809,11 @@ errors: No known data errors The Reiser file system, ReiserFS, was ported to &os; by &a.dumbbell;, and has been released under the - GNU Public License. + GPL . - The ReiserFS driver will permit the &os; kernel to - access ReiserFS file systems and read their contents, but not - write to them, currently. + The ReiserFS driver permits the &os; kernel to access + ReiserFS file systems and read their contents, but not + write to them. First, the kernel-loadable module needs to be loaded: From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 15:01:38 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 498B6659; Mon, 11 Feb 2013 15:01:38 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 2526E7A9; Mon, 11 Feb 2013 15:01:38 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1BF1cFZ036956; Mon, 11 Feb 2013 15:01:38 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1BF1cpO036953; Mon, 11 Feb 2013 15:01:38 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201302111501.r1BF1cpO036953@svn.freebsd.org> From: Dru Lavigne Date: Mon, 11 Feb 2013 15:01:38 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40948 - head/en_US.ISO8859-1/books/handbook/firewalls X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 15:01:38 -0000 Author: dru Date: Mon Feb 11 15:01:37 2013 New Revision: 40948 URL: http://svnweb.freebsd.org/changeset/doc/40948 Log: This patch addresses the following: - rewording to remove you, etc., i.e., and references to PPP - fixes xref - general tightening, removal of redundant paragraphs, and many fixes to grammos/typos - a reference to a non-existing logging section was removed - several comments were addressed and removed Approved by gjb (mentor) Modified: head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml Mon Feb 11 14:58:34 2013 (r40947) +++ head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml Mon Feb 11 15:01:37 2013 (r40948) @@ -36,39 +36,37 @@ Introduction - Firewalls make it possible to filter incoming and outgoing - traffic that flows through your system. A firewall can use one - or more sets of rules to inspect the network - packets as they come in or go out of your network connections - and either allows the traffic through or blocks it. The rules - of a firewall can inspect one or more characteristics of the - packets, including but not limited to the protocol type, the - source or destination host address, and the source or - destination port. - - Firewalls can greatly enhance the security of a host or a - network. They can be used to do one or more of - the following things: + Firewalls make it possible to filter the incoming and + outgoing traffic that flows through a system. A firewall can + use one or more sets of rules to inspect network + packets as they come in or go out of network connections and + either allows the traffic through or blocks it. The rules of + a firewall can inspect one or more characteristics of the + packets such as the protocol type, source or destination host + address, and source or destination port. + + Firewalls can enhance the security of a host or a network. + They can be used to do one or more of the following: - To protect and insulate the applications, services and - machines of your internal network from unwanted traffic - coming in from the public Internet. + Protect and insulate the applications, services, and + machines of an internal network from unwanted traffic from + the public Internet. - To limit or disable access from hosts of the internal + Limit or disable access from hosts of the internal network to services of the public Internet. - To support network address translation - (NAT), which allows your internal network + Support network address translation + (NAT), which allows an internal network to use private IP addresses and share a - single connection to the public Internet (either with a - single IP address or by a shared pool of - automatically assigned public addresses). + single connection to the public Internet using either a + single IP address or a shared pool of + automatically assigned public addresses. @@ -76,27 +74,27 @@ - How to properly define packet filtering rules. + How to define packet filtering rules. - The differences between the firewalls - built into &os;. + The differences between the firewalls built into + &os;. - How to use and configure the OpenBSD + How to use and configure the PF firewall. - How to use and configure - IPFILTER. + How to use and configure the + IPFILTER firewall. - How to use and configure - IPFW. + How to use and configure the + IPFW firewall. @@ -118,81 +116,68 @@ rulesets - There are two basic ways to create firewall rulesets: - inclusive or exclusive. An + A firewall ruleset can be either + exclusive or inclusive. An exclusive firewall allows all traffic through except for the traffic matching the ruleset. An inclusive firewall does the - reverse. It only allows traffic matching the rules through and + reverse as it only allows traffic matching the rules through and blocks everything else. - An inclusive firewall offers much better control of the - outgoing traffic, making it a better choice for systems that - offer services to the public Internet. It also controls the - type of traffic originating from the public Internet that can - gain access to your private network. All traffic that does - not match the rules, is blocked and logged by design. Inclusive - firewalls are generally safer than exclusive firewalls because - they significantly reduce the risk of allowing unwanted traffic - to pass through them. + An inclusive firewall offers better control of the outgoing + traffic, making it a better choice for systems that offer + services to the public Internet. It also controls the type of + traffic originating from the public Internet that can gain + access to a private network. All traffic that does not match + the rules is blocked and logged. Inclusive firewalls are + generally safer than exclusive firewalls because they + significantly reduce the risk of allowing unwanted + traffic. Unless noted otherwise, all configuration and example - rulesets in this chapter, create inclusive type - firewalls. + rulesets in this chapter create inclusive firewall + rulesets. Security can be tightened further using a stateful - firewall. This type of firewall keeps - track of which connections are opened through the firewall and - will only allow traffic through which either matches an existing - connection or opens a new one. The disadvantage of a stateful - firewall is that it can be vulnerable to Denial of Service - (DoS) attacks if a lot of new connections are - opened very fast. With most firewalls it is possible to use a - combination of stateful and non-stateful behavior to make an - optimal firewall for the site. + firewall. This type of firewall keeps track of open + connections and only allows traffic which either matches an + existing connection or opens a new, allowed connection. The + disadvantage of a stateful firewall is that it can be vulnerable + to Denial of Service (DoS) attacks if a lot + of new connections are opened very fast. Most firewalls use a + combination of stateful and non-stateful behavior. Firewall Packages - &os; has three different firewall packages built - into the base system. They are: IPFILTER - (also known as IPF), - IPFIREWALL (also known as - IPFW), and OpenBSD's - PacketFilter (also known as PF). - &os; also has two built in packages for traffic shaping - (basically controlling bandwidth usage): &man.altq.4; and - &man.dummynet.4;. Dummynet has traditionally been closely - tied with IPFW, and - ALTQ with - PF. Traffic shaping for IPFILTER can - currently be done with IPFILTER for NAT and filtering and - IPFW with &man.dummynet.4; - or by using PF with - ALTQ. - IPFW, and PF all use rules to control the access of packets - to and from your system, although they go about it different - ways and have a different rule syntax. - - The reason that &os; has multiple built in firewall packages - is that different people have different requirements and - preferences. No single firewall package is the best. - - The author prefers IPFILTER because its stateful rules are - much less complicated to use in a NAT - environment and it has a built in ftp proxy that simplifies the - rules to allow secure outbound FTP usage. + &os; has three firewalls built into the base system: + IPFILTER, also known as + IPF, IPFIREWALL, also + known as IPFW, and PF). + &os; also provides two traffic shapers for controlling bandwidth + usage: &man.altq.4; and &man.dummynet.4;. Dummynet has + traditionally been closely tied with IPFW, + and ALTQ with PF. Each + firewall uses rules to control the access of packets to and from + a &os; system, although they go about it in different ways and + each has a different rule syntax. + + &os; provides multiple firewalls in order to meet the + different requirements and preferences for a wide variety of + users. Each user should evaluate which firewall best meets + their needs. Since all firewalls are based on inspecting the values of selected packet control fields, the creator of the firewall - rulesets must have an understanding of how + ruleset must have an understanding of how TCP/IP works, what the different values in - the packet control fields are and how these values are used in a - normal session conversation. For a good explanation go to: - . + the packet control fields are, and how these values are used in + a normal session conversation. For a good introduction, refer + to Daryl's TCP/IP + Primer. @@ -207,8 +192,7 @@ - The OpenBSD Packet Filter (PF) and - <acronym>ALTQ</acronym> + PF and <acronym>ALTQ</acronym> firewall @@ -216,72 +200,65 @@ PF - As of July 2003 the OpenBSD firewall software application - known as PF was ported to &os; and - made available in the &os; Ports Collection. Released in 2004, - &os; 5.3 was the first release that contained - PF as an integrated part of the base system. - PF is a complete, full-featured firewall - that has optional support for ALTQ (Alternate - Queuing). ALTQ provides Quality of Service - (QoS) functionality. - - The OpenBSD Project does an outstanding job of - maintaining the PF FAQ. - As such, this section of the Handbook will focus on - PF as it pertains to &os; while providing - some general information regarding usage. For detailed usage - information please refer to the PF FAQ. + Since &os; 5.3, a ported version of OpenBSD's + PF firewall has been included as an + integrated part of the base system. PF is a + complete, full-featured firewall that has optional support for + ALTQ (Alternate Queuing), which provides + Quality of Service (QoS). + + Since the OpenBSD Project maintains the definitive + reference for PF in thePF FAQ, this + section of the Handbook focuses on PF as it + pertains to &os;, while providing some general usage + information. - More information about PF for &os; + More information about porting PF to &os; can be found at . Using the PF Loadable Kernel Modules - To load the PF Kernel Module add the following line to + In order to use PF, the PF kernel module must be first + loaded. Add the following line to /etc/rc.conf: pf_enable="YES" - Then run the startup script to load the module: + Then, run the startup script to load the module: &prompt.root; service pf start - Note that the PF Module will not load if it cannot find - the ruleset config file. The default location is + The PF module will not load if it cannot find the + ruleset configuration file. The default location is /etc/pf.conf. If the PF ruleset is - located somewhere else, PF can be instructed to look there - by adding a line like the following to - /etc/rc.conf: + located somewhere else, add a line to + /etc/rc.conf which specifies the full + path to the file: pf_rules="/path/to/pf.conf" The sample pf.conf can be found in /usr/share/examples/pf/. + class="directory">/usr/share/examples/pf/. The PF module can also be loaded manually from the command line: &prompt.root; kldload pf.ko - Logging support for PF is provided by the - pflog.ko and can be loaded by adding the + Logging support for PF is provided by + pflog.ko which can be loaded by adding the following line to /etc/rc.conf: pflog_enable="YES" - Then run the startup script to load the module: + Then, run the startup script to load the module: &prompt.root; service pflog start - If you need other PF features you will - need to compile PF support into the - kernel. @@ -305,37 +282,32 @@ device pfsync - While it is not necessary that you compile - PF support into the &os; kernel, you may - want to do so to take advantage of one of PF's advanced - features that is not included in the loadable module, namely - &man.pfsync.4;, which is a pseudo-device that exposes certain - changes to the state table used by PF. - It can be paired with &man.carp.4; to create failover - firewalls using PF. More information on - CARP can be found in - of the Handbook. - - The PF kernel options can be found in - /usr/src/sys/conf/NOTES and are - reproduced below: + While it is not necessary to compile + PF support into the &os; kernel, some of + PF's advanced features are not included in the loadable + module, namely &man.pfsync.4;, which is a pseudo-device that + exposes certain changes to the state table used by + PF. It can be paired with &man.carp.4; to + create failover firewalls using PF. More + information on CARP can be found in of the Handbook. + + The following PF kernel options can be + found in /usr/src/sys/conf/NOTES: device pf device pflog device pfsync - The device pf option enables support - for the Packet Filter firewall - (&man.pf.4;). - - The device pflog option enables the - optional &man.pflog.4; pseudo network device which can be - used to log traffic to a &man.bpf.4; descriptor. The - &man.pflogd.8; daemon can be used to store the logging - information to disk. + device pf enables PF support. + + device pflog enables the optional + &man.pflog.4; pseudo network device which can be used to log + traffic to a &man.bpf.4; descriptor. The &man.pflogd.8; + daemon can then be used to store the logging information to + disk. - The device pfsync option enables the - optional + device pfsync enables the optional &man.pfsync.4; pseudo-network device that is used to monitor state changes. @@ -343,8 +315,9 @@ device pfsync Available <filename>rc.conf</filename> Options - The following &man.rc.conf.5; statements configure - PF and &man.pflog.4; at boot: + The following &man.rc.conf.5; statements can be used to + configure PF and &man.pflog.4; at + boot: pf_enable="YES" # Enable PF (load module if required) pf_rules="/etc/pf.conf" # rules definition file for pf @@ -353,9 +326,9 @@ pflog_enable="YES" # start pflog_logfile="/var/log/pflog" # where pflogd should store the logfile pflog_flags="" # additional flags for pflogd startup - If you have a LAN behind this firewall and have to forward - packets for the computers on the LAN or want to do NAT, you - will need the following option as well: + If there is a LAN behind the firewall and packets need to + be forwarded for the computers on the LAN, or NAT is required, + add the following option: gateway_enable="YES" # Enable as LAN gateway @@ -363,40 +336,40 @@ pflog_flags="" # additi Creating Filtering Rules - PF reads its configuration rules from - &man.pf.conf.5; (/etc/pf.conf by - default) and it modifies, drops, or passes packets according - to the rules or definitions specified there. The &os; - installation includes several sample files located in - /usr/share/examples/pf/. Please refer - to the PF - FAQ for complete coverage of PF - rulesets. + By default, PF reads its configuration + rules from /etc/pf.conf and modifies, + drops, or passes packets according to the rules or definitions + specified in this file. The &os; installation includes + several sample files located in + /usr/share/examples/pf/. Refer to the + PF FAQ for + complete coverage of PF rulesets. - When browsing the PF FAQ, - please keep in mind that different versions of &os; can - contain different versions of PF. Currently, - &os; 8.X and prior is - using the same version of PF as + When reading the PF FAQ, + keep in mind that different versions of &os; contain + different versions of PF. Currently, + &os; 8.X and prior is using + the same version of PF as OpenBSD 4.1. &os; 9.X and later is using the same version of PF as OpenBSD 4.5. The &a.pf; is a good place to ask questions about - configuring and running the PF - firewall. Do not forget to check the mailing list archives - before asking questions! + configuring and running the PF firewall. + Do not forget to check the mailing list archives before asking + questions. Working with PF - Use &man.pfctl.8; to control PF. Below - are some useful commands (be sure to review the &man.pfctl.8; - man page for all available options): + To control PF, use &man.pfctl.8;. + Below are some useful options to this command. Review + &man.pfctl.8; for a description of all available + options: @@ -411,35 +384,35 @@ pflog_flags="" # additi pfctl - Enable PF + Enable PF. pfctl - Disable PF + Disable PF. pfctl all /etc/pf.conf - Flush all rules (nat, filter, state, table, etc.) - and reload from the file - /etc/pf.conf + Flush all NAT, filter, state, and table + rules and reload + /etc/pf.conf. pfctl [ rules | nat state ] - Report on the filter rules, nat rules, or state - table + Report on the filter rules, NAT rules, or state + table. pfctl /etc/pf.conf Check /etc/pf.conf for - errors, but do not load ruleset + errors, but do not load ruleset. @@ -449,11 +422,11 @@ pflog_flags="" # additi Enabling <acronym>ALTQ</acronym> - ALTQ is only available by compiling - support for it into the &os; kernel. ALTQ - is not supported by all of the available network card drivers. - Please see the &man.altq.4; manual page for a list of drivers - that are supported in your release of &os;. + ALTQ is only available by compiling its + support into the &os; kernel. ALTQ is not + supported by all network card drivers. Refer to &man.altq.4; + for a list of drivers that are supported by the release of + &os;. The following kernel options will enable ALTQ and add additional @@ -473,28 +446,27 @@ options ALTQ_NOPCC # Requir options ALTQ_CBQ enables Class Based Queuing (CBQ). CBQ - allows you to divide a connection's bandwidth into different + can be used to divide a connection's bandwidth into different classes or queues to prioritize traffic based on filter rules. options ALTQ_RED enables Random Early Detection (RED). RED is - used to avoid network congestion. RED - does this by measuring the length of the queue and comparing - it to the minimum and maximum thresholds for the queue. If - the queue is over the maximum all new packets will be dropped. - True to its name, RED drops packets from - different connections randomly. + used to avoid network congestion by measuring the length of + the queue and comparing it to the minimum and maximum + thresholds for the queue. If the queue is over the maximum, + all new packets will be dropped. RED drops + packets from different connections randomly. options ALTQ_RIO enables Random Early Detection In and Out. options ALTQ_HFSC enables the Hierarchical Fair Service Curve Packet - Scheduler. For more information about - HFSC see: . + Scheduler HFSC. For more + information, refer to . options ALTQ_PRIQ enables Priority Queuing @@ -517,51 +489,46 @@ options ALTQ_NOPCC # Requir IPFILTER - The author of IPFILTER is Darren Reed. IPFILTER is not - operating system dependent: it is an open source application and + IPFILTER is a cross-platform, open source firewall which has been ported to &os;, NetBSD, OpenBSD, &sunos;, HP/UX, and - &solaris; operating systems. IPFILTER is actively being - supported and maintained, with updated versions being released - regularly. + &solaris; operating systems. IPFILTER is based on a kernel-side firewall and NAT mechanism that can be controlled and monitored by userland interface programs. The firewall rules - can be set or deleted with the &man.ipf.8; utility. The - NAT rules can be set or deleted with the - &man.ipnat.8; utility. The &man.ipfstat.8; utility can print - run-time statistics for the kernel parts of IPFILTER. The - &man.ipmon.8; program can log IPFILTER actions to the system - log files. + can be set or deleted using &man.ipf.8;. The + NAT rules can be set or deleted using + &man.ipnat.8;. Run-time statistics for the kernel parts of + IPFILTER can be printed using &man.ipfstat.8;. To log IPFILTER + actions to the system log files, use &man.ipmon.8;. IPF was originally written using a rule processing logic - of the last matching rule wins and used only - stateless type of rules. Over time IPF has been enhanced to - include a quick option and a stateful - keep state option which drastically modernized - the rules processing logic. IPF's official documentation covers - only the legacy rule coding parameters and rule file processing - logic. The modernized functions are only included as additional - options, completely understating their benefits in producing - a far superior and more secure firewall. + of the last matching rule wins and only used + stateless rules. Over time, IPF has been enhanced to include a + quick option and a stateful + keep state option which modernized the rules + processing logic. IPF's official documentation covers only the + legacy rule coding parameters and rule file processing logic and + the modernized functions are only included as additional + options. The instructions contained in this section are based on - using rules that contain the quick option and the - stateful keep state option. This is the basic - framework for coding an inclusive firewall ruleset. - - For detailed explanation of the legacy rules processing - method see: + using rules that contain quick and + keep state as these provide the basic framework + for configuring an inclusive firewall ruleset. + + For a detailed explanation of the legacy rules processing + method, refer to and . + url="http://coombs.anu.edu.au/~avalon/ip-filter.html">. The IPF FAQ is at . + url="http://www.phildev.net/ipf/index.html">. - A searchable archive of the open-source IPFilter mailing - list is available at . + A searchable archive of the IPFilter mailing list is + available at . Enabling IPF @@ -572,17 +539,15 @@ options ALTQ_NOPCC # Requir enabling - IPF is included in the basic &os; install as a separate - run time loadable module. The system will dynamically load - the IPF kernel loadable module when the - rc.conf statement - ipfilter_enable="YES" is used. The - loadable module was created with logging enabled and the - default pass all options. There is no - need to compile IPF into the &os; kernel just to change the - default to block all. This can be done - just by adding a block all rule at the - end of your ruleset. + IPF is included in the basic &os; install as a kernel + loadable module. The system will dynamically load + this module at boot time when + ipfilter_enable="YES" is added to + rc.conf. The module enables logging and + default pass all. To change the + default to block all, add a + block all rule at the end of the + ruleset. @@ -612,15 +577,10 @@ options ALTQ_NOPCC # Requir kernel options - It is not a mandatory requirement to enable IPF by - compiling the following options into the &os; kernel. It is - only presented here as background information. Compiling IPF - into the kernel causes the loadable module to never be - used. - - Sample kernel config IPF option statements are in the - /usr/src/sys/conf/NOTES kernel source - and are reproduced here: + For users who prefer to statically compile IPF support + into a custom kernel, the following IPF option statements, + listed in /usr/src/sys/conf/NOTES, are + available: options IPFILTER options IPFILTER_LOG @@ -629,15 +589,14 @@ options IPFILTER_DEFAULT_BLOCKoptions IPFILTER enables support for the IPFILTER firewall. - options IPFILTER_LOG enables the option - to have IPF log traffic by writing to the - ipl packet logging + options IPFILTER_LOG enables IPF + logging using the ipl packet logging pseudo—device for every rule that has the log keyword. options IPFILTER_DEFAULT_BLOCK changes - the default behavior so any packet not matching a firewall - pass rule gets blocked. + the default behavior so that any packet not matching a + firewall pass rule gets blocked. These settings will take effect only after installing a kernel that has been built with the above options set. @@ -657,9 +616,9 @@ ipmon_flags="-Ds" # D = # v = log tcp window, ack, seq # n = map IP & port to names - If there is a LAN behind this firewall that uses the - reserved private IP address ranges, the following lines will - have to be added to enable NAT + If there is a LAN behind the firewall that uses the + reserved private IP address ranges, the following lines have + to be added to enable NAT functionality: gateway_enable="YES" # Enable as LAN gateway @@ -672,36 +631,36 @@ ipnat_rules="/etc/ipnat.rules" # rule ipf - The &man.ipf.8; command is used to load your ruleset file. - Your custom rules would normally be placed in a file, and the - following command could then be used to replace in mass the - currently running firewall rules: + To load the ruleset file, use &man.ipf.8;. Custom rules + are normally placed in a file, and the following command can + be used to replace the currently running firewall + rules: &prompt.root; ipf -Fa -f /etc/ipf.rules - means flush all internal rules + flushes all the internal rules tables. - means this is the file to read for - the rules to load. + specifies the file containing the + rules to load. - This gives you the ability to make changes to your custom + This provides the ability to make changes to a custom rules file, run the above IPF command, and thus update the - running firewall with a fresh copy of all the rules without - having to reboot the system. This method is very convenient - for testing new rules as the procedure can be executed as many - times as needed. - - See the &man.ipf.8; manual page for details on the other - flags available with this command. - - The &man.ipf.8; command expects the rules file to be a - standard text file. It will not accept a rules file written - as a script with symbolic substitution. + running firewall with a fresh copy of the rules without having + to reboot the system. This method is convenient for testing + new rules as the procedure can be executed as many times as + needed. + + Refer to &man.ipf.8; for details on the other flags + available with this command. + + &man.ipf.8; expects the rules file to be a standard text + file. It will not accept a rules file written as a script + with symbolic substitution. - There is a way to build IPF rules that utilizes the power + There is a way to build IPF rules that utilize the power of script symbolic substitution. For more information, see - . + . @@ -717,15 +676,15 @@ ipnat_rules="/etc/ipnat.rules" # rule The default behavior of &man.ipfstat.8; is to retrieve and display the totals of the accumulated statistics gathered - as a result of applying the user coded rules against packets - going in and out of the firewall since it was last started, - or since the last time the accumulators were reset to zero - using ipf -Z. + by applying the rules against packets going in and out of the + firewall since it was last started, or since the last time the + accumulators were reset to zero using ipf + -Z. - See the &man.ipfstat.8; manual page for details. + Refer to &man.ipfstat.8; for details. - The default &man.ipfstat.8; command output will look - something like this: + The default &man.ipfstat.8; output will look something + like this: input packets: blocked 99286 passed 1255609 nomatch 14686 counted 0 output packets: blocked 4200 passed 1284345 nomatch 14687 counted 0 @@ -751,10 +710,10 @@ ipnat_rules="/etc/ipnat.rules" # rule installed and in use by the kernel. ipfstat -in displays the inbound - internal rules table with rule number. + internal rules table with rule numbers. ipfstat -on displays the outbound - internal rules table with the rule number. + internal rules table with rule numbers. The output will look something like this: @@ -776,16 +735,15 @@ ipnat_rules="/etc/ipnat.rules" # rule 354727 block out on dc0 from any to any 430918 pass out quick on dc0 proto tcp/udp from any to any keep state - One of the most important functions of - ipfstat is the - flag which displays the state table in a way similar to the - way &man.top.1; shows the &os; running process table. When - your firewall is under attack, this function gives you the - ability to identify, drill down to, and see the attacking - packets. The optional sub-flags give the ability to select - the destination or source IP, port, or protocol that you want - to monitor in real time. See the &man.ipfstat.8; manual page - for details. + One of the most important options of + ipfstat is which + displays the state table in a way similar to how &man.top.1; + shows the &os; running process table. When a firewall is + under attack, this function provides the ability to identify + and see the attacking packets. The optional sub-flags give + the ability to select the destination or source IP, port, or + protocol to be monitored in real time. Refer to + &man.ipfstat.8; for details. @@ -801,55 +759,51 @@ ipnat_rules="/etc/ipnat.rules" # rule In order for ipmon to work properly, the kernel option IPFILTER_LOG must be - turned on. This command has two different modes that it can - be used in. Native mode is the default mode when the command - is typed on the command line without the - flag. - - Daemon mode is for when a continuous - system log file is desired, so that logging of past events - may be reviewed. This is how &os; and IPFILTER are configured - to work together. &os; has a built in facility to - automatically rotate system logs. That is why outputting the - log information to &man.syslogd.8; is better than the default - of outputting to a regular file. In the default - rc.conf, the - ipmon_flags statement uses the - flags: + turned on. This command has two different modes. Native mode + is the default mode when the command is used without + . + + Daemon mode provides a continuous system log file so that + logging of past events may be reviewed. &os; has a built in + facility to automatically rotate system logs. This is why + outputting the log information to &man.syslogd.8; is better + than the default of outputting to a regular file. The default + rc.conf + ipmon_flags statement uses + : ipmon_flags="-Ds" # D = start as daemon # s = log to syslog # v = log tcp window, ack, seq # n = map IP & port to names - The benefits of logging are obvious. It provides the - ability to review, after the fact, information such as which - packets had been dropped, what addresses they came from and - where they were going. These can all provide a significant - edge in tracking down attackers. + Logging provides the ability to review, after the fact, + information such as which packets were dropped, what addresses + they came from and where they were going. These can all + provide a significant edge in tracking down attackers. Even with the logging facility enabled, IPF will not - generate any rule logging on its own. The firewall - administrator decides what rules in the ruleset he wants to - log and adds the log keyword to those rules. Normally only - deny rules are logged. - - It is very customary to include a default deny everything - rule with the log keyword included as your last rule in the - ruleset. This makes it possible to see all the packets that - did not match any of the rules in the ruleset. + generate any rule logging by default. The firewall + administrator decides which rules in the ruleset should be + logged and adds the log keyword to those rules. Normally, + only deny rules are logged. + + It is customary to include a default deny + everything rule with the log keyword included as the + last rule in the ruleset. This makes it possible to see all + the packets that did not match any of the rules in the + ruleset. IPMON Logging - Syslogd uses its own special - method for segregation of log data. It uses special groupings - called facility and level. - IPMON in mode uses - local0 as the facility - name by default. The following levels can be used to further - segregate the logged data if desired: + &man.syslogd.8; uses its own method for segregation of log + data. It uses groupings called facility and + level. By default, IPMON in + mode uses local0 as + the facility name. The following levels can be + used to further segregate the logged data: LOG_INFO - packets logged using the "log" keyword as the action rather than pass or block. LOG_NOTICE - packets logged which are also passed @@ -858,37 +812,31 @@ LOG_ERR - packets which have been logged - To setup IPFILTER to log all data to - /var/log/ipfilter.log, the file will - need to be created beforehand. The following command will - do that: + In order to setup IPFILTER to log all data to + /var/log/ipfilter.log, first + create the empty file: &prompt.root; touch /var/log/ipfilter.log - The &man.syslogd.8; function is controlled by definition - statements in /etc/syslog.conf. - This file offers considerable - flexibility in how syslog will - deal with system messages issued by software applications - like IPF. + &man.syslogd.8; is controlled by definition statements in + /etc/syslog.conf. This file offers + considerable flexibility in how + syslog will deal with system + messages issued by software applications like IPF. - Add the following statement to + To write all logged messages to the specified file, + add the following statement to /etc/syslog.conf: local0.* /var/log/ipfilter.log - The local0.* - means to write all the logged messages to the coded - file location. - - To activate the changes to /etc/syslog.conf - you can reboot or bump the &man.syslogd.8; - daemon into re-reading /etc/syslog.conf - by running service syslogd reload + To activate the changes and instruct &man.syslogd.8; + to read the modified /etc/syslog.conf, + run service syslogd reload. Do not forget to change /etc/newsyslog.conf to rotate the new - log created above. + log file. @@ -906,16 +854,16 @@ LOG_ERR - packets which have been logged The time of packet receipt. This is in the form HH:MM:SS.F, for hours, minutes, seconds, and fractions - of a second (which can be several digits long). *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 19:35:07 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2A505CF4; Mon, 11 Feb 2013 19:35:07 +0000 (UTC) (envelope-from flo@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 1801997E; Mon, 11 Feb 2013 19:35:07 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1BJZ615019106; Mon, 11 Feb 2013 19:35:06 GMT (envelope-from flo@svn.freebsd.org) Received: (from flo@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1BJZ6RW019105; Mon, 11 Feb 2013 19:35:06 GMT (envelope-from flo@svn.freebsd.org) Message-Id: <201302111935.r1BJZ6RW019105@svn.freebsd.org> From: Florian Smeets Date: Mon, 11 Feb 2013 19:35:06 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40949 - head/en_US.ISO8859-1/books/handbook/desktop X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 19:35:07 -0000 Author: flo (ports committer) Date: Mon Feb 11 19:35:06 2013 New Revision: 40949 URL: http://svnweb.freebsd.org/changeset/doc/40949 Log: Compiling Chromium can no longer be seen as medium as it has more dependencies than firefox now, and that has been in the heavy category for a long time. Suggested by: Jan Beich Approved by: gjb Modified: head/en_US.ISO8859-1/books/handbook/desktop/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/desktop/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/desktop/chapter.xml Mon Feb 11 15:01:37 2013 (r40948) +++ head/en_US.ISO8859-1/books/handbook/desktop/chapter.xml Mon Feb 11 19:35:06 2013 (r40949) @@ -273,7 +273,7 @@ Chromium medium - medium + heavy Requires Gtk+ From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 21:04:43 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 66BC840F; Mon, 11 Feb 2013 21:04:43 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 0782CE06; Mon, 11 Feb 2013 21:04:42 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.6/8.14.6) with ESMTP id r1BL4g1b028673; Mon, 11 Feb 2013 14:04:42 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.6/8.14.6/Submit) with ESMTP id r1BL4g6N028670; Mon, 11 Feb 2013 14:04:42 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Mon, 11 Feb 2013 14:04:42 -0700 (MST) From: Warren Block To: Dru Lavigne Subject: Re: svn commit: r40946 - head/en_US.ISO8859-1/books/handbook/geom In-Reply-To: <201302111450.r1BEoXIR033682@svn.freebsd.org> Message-ID: References: <201302111450.r1BEoXIR033682@svn.freebsd.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Mon, 11 Feb 2013 14:04:42 -0700 (MST) Cc: svn-doc-head@freebsd.org, svn-doc-all@freebsd.org, doc-committers@freebsd.org X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 21:04:43 -0000 On Mon, 11 Feb 2013, Dru Lavigne wrote: > Author: dru > Date: Mon Feb 11 14:50:33 2013 > New Revision: 40946 > URL: http://svnweb.freebsd.org/changeset/doc/40946 > > Log: > This patch addresses the following: > > - fixes xref tags > > - some tightening and removing of redundancy > > - fixed some confusion in glabel section > > Approved by gjb (mentor) > > Modified: > head/en_US.ISO8859-1/books/handbook/geom/chapter.xml ... Uh oh. Heading for the mirror section, which I and HRS revised recently and is still seared into my memory. Comments inline. > &prompt.root; echo "/dev/stripe/st0a /stripe ufs rw 2 2" \ > @@ -249,8 +248,8 @@ Done. > replace the failed drive without user interruption. > > Two common situations are illustrated in these examples. > - The first is creating a mirror out of two new drives and using > - it as a replacement for an existing single drive. The second > + The first creates a mirror out of two new drives and uses it > + as a replacement for an existing single drive. The second > example creates a mirror on a single new drive, copies the old > drive's data to it, then inserts the old drive into the > mirror. While this procedure is slightly more complicated, it > @@ -317,28 +316,28 @@ Done. > used to replace the old single disk. > > &man.gmirror.8; requires a kernel module, > - geom_mirror.ko, either built into the > - kernel or loaded at boot- or run-time. Manually load the > - kernel module now: > + geom_mirror.ko, either compiled into a > + custom kernel or loaded at boot- or run-time. To manually > + load the kernel module now: That last sentence was right the previous way. It's not "how to do it", it's "do this because the following instructions require it." > &prompt.root; gmirror load > > - Create the mirror with the two new drives. > + To create the mirror with the two new drives. As above, this is (was) an imperative. "Do this, or feel the sting of utter failure!" > &prompt.root; gmirror label -v gm0 /dev/ada1 /dev/ada2 > > gm0 is a user-chosen device name > assigned to the new mirror. After the mirror has been > - started, this device name will appear in the > - /dev/mirror/ directory. > + started, this device name will appear in > + /dev/mirror/. > MBR and bsdlabel partition tables can now be created on > the mirror with &man.gpart.8;. Here we show a traditional > split-filesystem layout, with partitions for > /, swap, /var, > /tmp, and /usr. A > - single / filesystem and a swap partition > - will also work. > + single / and a swap partition will also > + work. Without the "filesystem" word, it is not as clear what the / refers to; it could be read as a literal slash, or a directory, or a file. > Partitions on the mirror do not have to be the same size > as those on the existing disk, but they must be large enough > @@ -384,8 +383,8 @@ Done. > &prompt.root; newfs -U /dev/mirror/gm0s1e > &prompt.root; newfs -U /dev/mirror/gm0s1f > > - Filesystems from the original disk > - (ada0) can now be copied onto the > + Filesystems from the original > + ada0 disk can now be copied onto the > mirror with &man.dump.8; and &man.restore.8;. > > &prompt.root; mount /dev/mirror/gm0s1a /mnt > @@ -419,8 +418,8 @@ Done. > are identical, it does not matter which is selected to > boot. > > - See the > - Troubleshooting > + See the + linkend="gmirror-troubleshooting">Troubleshooting > section if there are problems booting. Powering down and > disconnecting the original ada0 disk > will allow it to be kept as an offline backup. > @@ -432,23 +431,23 @@ Done. > > Creating a Mirror with an Existing Drive > > - In this example, &os; has already been installed on a > - single disk, ada0. A new disk, > + In this example, &os; has been installed on a single > + disk, ada0. A new disk, Why remove the "already"? That's part of what this example is trying to explain, how to create a mirror when FreeBSD is already on one of two drives. > ada1, has been connected to the > system. A one-disk mirror will be created on the new disk, > - the existing system copied onto it, and then the old disk will be > - inserted into the mirror. This slightly complex procedure is > - required because &man.gmirror.8; needs to put a 512-byte block > - of metadata at the end of each disk, and the existing > - ada0 has usually had all of its space > + the existing system copied onto it, and then the old disk will > + be inserted into the mirror. This slightly complex procedure > + is required because &man.gmirror.8; needs to put a 512-byte > + block of metadata at the end of each disk, and the existing > + ada0 usually has all of its space > already allocated. I think "has usually had all of of its space already allocated" is the correct tense. > - Load the &man.gmirror.8; kernel module. > + Load the &man.gmirror.8; kernel module: It's not required that everything that is about to show an example lead up to it with a colon. It makes for staccato reading, but people seem to like that, so okay. > &prompt.root; gmirror load > > Check the media size of the original disk with > - &man.diskinfo.8;. > + &man.diskinfo.8;: > > &prompt.root; diskinfo -v ada0 | head -n3 > /dev/ada0 > @@ -461,11 +460,11 @@ Done. > size. This drive does not store any data, but is used only to > limit the size of the mirror. When &man.gmirror.8; creates > the mirror, it will restrict the capacity to the size of > - gzero.nop even if the new drive > + gzero.nop, even if the new drive > (ada1) has more space. Note that the > 1000204821504 in the second line > - should be equal to ada0's media size > - as shown by &man.diskinfo.8; above. > + should be equal to the size of ada0 > + as shown by &man.diskinfo.8;. "media size" is (was) mentioned to help the user find the right value in diskinfo(8) output. > &prompt.root; geom zero load > &prompt.root; gnop create -s 1000204821504 gzero > @@ -502,7 +501,7 @@ Done. > be explained later. > > In either case, partition tables on the primary disk > - should be copied first. It can be done by using &man.gpart.8; > + should be copied first using the &man.gpart.8; > backup and restore > subcommands. Okay. But I suggest s/using/with/. > @@ -527,8 +526,8 @@ BSD 8 > 6 freebsd-ufs 130023424 838860800 > 7 freebsd-ufs 968884224 984640881 > > - If the whole disk was used in the output of &man.gpart.8; > - show, the capacity in these partition > + If the whole disk shows as used in the output of > + gpart show, the capacity in these partition > tables must be reduced by one sector. Edit the two files, > reducing the size of both the slice and last partition by one. > These are the last numbers in each listing. > @@ -550,13 +549,13 @@ BSD 8 > disk, these two files can be used without modification. Suggestion for specifics: "If the output of gpart show shows no free space at the end of the disk, the size of both the slice and the last partition must be reduced by one sector." > Now restore the partition table into > - mirror/gm0. > + mirror/gm0: > > &prompt.root; gpart restore mirror/gm0 < table.ada0 > &prompt.root; gpart restore mirror/gm0s1 < table.ada0s1 > > - Check the partition table with the &man.gpart.8; > - show. This example has > + Check the partition table with > + gpart show. This example has > gm0s1a for /, > gm0s1d for /var, > gm0s1e for /usr, > @@ -707,8 +706,7 @@ mirror/gm0 COMPLETE ada1 (ACTIVE) > > BIOS settings may have to be changed to boot from one > of the new mirrored drives. Either mirror drive can be > - used for booting. As components of a mirror, they contain > - identical data. > + used for booting as they contain identical data. > Needs a comma after "booting", I think. > > @@ -742,10 +740,10 @@ mountroot> > Forgetting to load the > geom_mirror module in > /boot/loader.conf can cause this > - problem. To fix it, boot from a &os;-9 or later CD or USB > - stick and choose Shell at the first > - prompt. Then load the mirror module and mount the mirror > - device: > + problem. To fix it, boot from a &os; 9.0 or later > + installation media and choose Shell at > + the first prompt. Then load the mirror module and mount > + the mirror device: > > &prompt.root; gmirror load > &prompt.root; mount /dev/mirror/gm0s1a /mnt > @@ -759,14 +757,14 @@ mountroot> > > Other problems that cause error 19 > require more effort to fix. Enter > - ufs:/dev/ada0s1a at the prompt. > - Although the system should boot from > + ufs:/dev/ada0s1a at the boot loader > + prompt. Although the system should boot from > ada0, another prompt to select a > shell appears because /etc/fstab is > incorrect. Press the Enter key at the prompt. Undo the > modifications so far by reverting > /etc/fstab, mounting filesystems from > - the original disk (ada0) instead > + the original ada0 instead > of the mirror. Reboot the system and try the procedure > again. ada0 is (was) mentioned parenthetically because it was the example, not necessarily what the user will have. From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 21:12:00 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id ED855899; Mon, 11 Feb 2013 21:12:00 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id C5D5EE61; Mon, 11 Feb 2013 21:12:00 +0000 (UTC) Received: from pakbsde14.localnet (unknown [38.105.238.108]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 0C625B911; Mon, 11 Feb 2013 16:12:00 -0500 (EST) From: John Baldwin To: Eitan Adler Subject: Re: svn commit: r40944 - head/en_US.ISO8859-1/books/arch-handbook/driverbasics Date: Mon, 11 Feb 2013 11:27:57 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p22; KDE/4.5.5; amd64; ; ) References: <201302111346.r1BDkVpm012937@svn.freebsd.org> In-Reply-To: <201302111346.r1BDkVpm012937@svn.freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201302111127.57887.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 11 Feb 2013 16:12:00 -0500 (EST) Cc: svn-doc-head@freebsd.org, svn-doc-all@freebsd.org, doc-committers@freebsd.org X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 21:12:01 -0000 On Monday, February 11, 2013 8:46:31 am Eitan Adler wrote: > Author: eadler > Date: Mon Feb 11 13:46:30 2013 > New Revision: 40944 > URL: http://svnweb.freebsd.org/changeset/doc/40944 > > Log: > Fix indentation and whitespace > > Translators may ignore > > Approved by: bcr (mentor) > > Modified: > head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml > > Modified: head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml > ============================================================================== > --- head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml Mon Feb 11 13:46:28 2013 (r40943) > +++ head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml Mon Feb 11 13:46:30 2013 (r40944) > @@ -148,10 +148,10 @@ KMOD=skeleton > .include <bsd.kmod.mk> > > Running make with this makefile > - will create a file skeleton.ko that can > - be loaded into the kernel by typing: > -&prompt.root; kldload -v ./skeleton.ko > - > + will create a file skeleton.ko that can > + be loaded into the kernel by typing: > + > + &prompt.root; kldload -v ./skeleton.ko > > > > @@ -164,8 +164,8 @@ KMOD=skeleton > accesses a device node. The /dev/MAKEDEV > script makes most of the device nodes for your system but if you > are doing your own driver development it may be necessary to > - create your own device nodes with mknod. > - > + create your own device nodes with > + mknod. > > > Creating Static Device Nodes > @@ -422,8 +422,7 @@ Closing device "echo". > (partition) to two devices with different semantics significantly > complicated the relevant kernel code &os; dropped support for > cached disk devices as part of the modernization of the disk I/O > - infrastructure. > - > + infrastructure. > > > All the bits about MAKEDEV and mknod should be removed. They haven't been necessary since 4.x. That means all of section 9.3 can be removed. -- John Baldwin From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 21:36:01 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1756ED8; Mon, 11 Feb 2013 21:36:01 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 0A983F79; Mon, 11 Feb 2013 21:36:01 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1BLa06N055293; Mon, 11 Feb 2013 21:36:00 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1BLa0na055292; Mon, 11 Feb 2013 21:36:00 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201302112136.r1BLa0na055292@svn.freebsd.org> From: Eitan Adler Date: Mon, 11 Feb 2013 21:36:00 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40950 - in head/en_US.ISO8859-1/htdocs: . FAQ X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 21:36:01 -0000 Author: eadler Date: Mon Feb 11 21:36:00 2013 New Revision: 40950 URL: http://svnweb.freebsd.org/changeset/doc/40950 Log: Remove FAQ directory (and redirect) which will be replaced by a case independent redirect. Discussed on: -doc clusteradm bug: #160 Approved by: jkois (mentor) Deleted: head/en_US.ISO8859-1/htdocs/FAQ/ Modified: head/en_US.ISO8859-1/htdocs/Makefile Modified: head/en_US.ISO8859-1/htdocs/Makefile ============================================================================== --- head/en_US.ISO8859-1/htdocs/Makefile Mon Feb 11 19:35:06 2013 (r40949) +++ head/en_US.ISO8859-1/htdocs/Makefile Mon Feb 11 21:36:00 2013 (r40950) @@ -49,7 +49,6 @@ DATA+= vendors.html # Subdirectories # XML -SUBDIR= FAQ SUBDIR+= advocacy SUBDIR+= commercial SUBDIR+= community From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 21:50:50 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C81BD517; Mon, 11 Feb 2013 21:50:50 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id AC50B96; Mon, 11 Feb 2013 21:50:50 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1BLoorl058973; Mon, 11 Feb 2013 21:50:50 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1BLooZY058972; Mon, 11 Feb 2013 21:50:50 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201302112150.r1BLooZY058972@svn.freebsd.org> From: Dru Lavigne Date: Mon, 11 Feb 2013 21:50:50 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40951 - head/en_US.ISO8859-1/books/handbook/geom X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 21:50:50 -0000 Author: dru Date: Mon Feb 11 21:50:50 2013 New Revision: 40951 URL: http://svnweb.freebsd.org/changeset/doc/40951 Log: Patch to address wblock's comments. Approved by: gjb (mentor) Modified: head/en_US.ISO8859-1/books/handbook/geom/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/geom/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/geom/chapter.xml Mon Feb 11 21:36:00 2013 (r40950) +++ head/en_US.ISO8859-1/books/handbook/geom/chapter.xml Mon Feb 11 21:50:50 2013 (r40951) @@ -316,13 +316,13 @@ Done. used to replace the old single disk. &man.gmirror.8; requires a kernel module, - geom_mirror.ko, either compiled into a - custom kernel or loaded at boot- or run-time. To manually - load the kernel module now: + geom_mirror.ko, either built into the + kernel or loaded at boot- or run-time. Manually load the + kernel module now: &prompt.root; gmirror load - To create the mirror with the two new drives. + Create the mirror with the two new drives: &prompt.root; gmirror label -v gm0 /dev/ada1 /dev/ada2 @@ -336,8 +336,8 @@ Done. split-filesystem layout, with partitions for /, swap, /var, /tmp, and /usr. A - single / and a swap partition will also - work. + single / filesystem and a swap partition + will also work. Partitions on the mirror do not have to be the same size as those on the existing disk, but they must be large enough @@ -431,15 +431,15 @@ Done. Creating a Mirror with an Existing Drive - In this example, &os; has been installed on a single - disk, ada0. A new disk, + In this example, &os; has already been installed on a + single disk, ada0. A new disk, ada1, has been connected to the system. A one-disk mirror will be created on the new disk, the existing system copied onto it, and then the old disk will be inserted into the mirror. This slightly complex procedure is required because &man.gmirror.8; needs to put a 512-byte block of metadata at the end of each disk, and the existing - ada0 usually has all of its space + ada0 has usually had all of its space already allocated. Load the &man.gmirror.8; kernel module: @@ -463,8 +463,8 @@ Done. gzero.nop, even if the new drive (ada1) has more space. Note that the 1000204821504 in the second line - should be equal to the size of ada0 - as shown by &man.diskinfo.8;. + should be equal to ada0's media size + as shown by &man.diskinfo.8; above. &prompt.root; geom zero load &prompt.root; gnop create -s 1000204821504 gzero @@ -501,7 +501,7 @@ Done. be explained later. In either case, partition tables on the primary disk - should be copied first using the &man.gpart.8; + should be copied first with the &man.gpart.8; backup and restore subcommands. @@ -526,11 +526,12 @@ BSD 8 6 freebsd-ufs 130023424 838860800 7 freebsd-ufs 968884224 984640881 - If the whole disk shows as used in the output of - gpart show, the capacity in these partition - tables must be reduced by one sector. Edit the two files, - reducing the size of both the slice and last partition by one. - These are the last numbers in each listing. + If the output of gpart show shows no + free space at the end of the disk, the size of both the slice + and the last partition must be reduced by one sector. Edit + the two files, reducing the size of both the slice and last + partition by one. These are the last numbers in each + listing. &prompt.root; cat table.ada0 MBR 4 @@ -706,7 +707,7 @@ mirror/gm0 COMPLETE ada1 (ACTIVE) BIOS settings may have to be changed to boot from one of the new mirrored drives. Either mirror drive can be - used for booting as they contain identical data. + used for booting, as they contain identical data. @@ -764,7 +765,7 @@ mountroot> incorrect. Press the Enter key at the prompt. Undo the modifications so far by reverting /etc/fstab, mounting filesystems from - the original ada0 instead + the original disk (ada0) instead of the mirror. Reboot the system and try the procedure again. From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 23:21:09 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id BE9442EC; Mon, 11 Feb 2013 23:21:09 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id A2B356D7; Mon, 11 Feb 2013 23:21:09 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1BNL9Y5087841; Mon, 11 Feb 2013 23:21:09 GMT (envelope-from linimon@svn.freebsd.org) Received: (from linimon@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1BNL9Bu087840; Mon, 11 Feb 2013 23:21:09 GMT (envelope-from linimon@svn.freebsd.org) Message-Id: <201302112321.r1BNL9Bu087840@svn.freebsd.org> From: Mark Linimon Date: Mon, 11 Feb 2013 23:21:09 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40952 - head/en_US.ISO8859-1/articles/portbuild X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 23:21:09 -0000 Author: linimon Date: Mon Feb 11 23:21:09 2013 New Revision: 40952 URL: http://svnweb.freebsd.org/changeset/doc/40952 Log: Reflect the fact that src branch definitions have moved to admin/admin.conf, and that makeworld, mkbindist, zbackup, and zexpire have all moved to admin/scripts/ . This fixes up the three sections on dealing with changes to branches, but the "new architecture" section is still a mess. While here, stamp out more uses of /var/portbuild in favor of /a/portbuild. Modified: head/en_US.ISO8859-1/articles/portbuild/article.xml Modified: head/en_US.ISO8859-1/articles/portbuild/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/portbuild/article.xml Mon Feb 11 21:50:50 2013 (r40951) +++ head/en_US.ISO8859-1/articles/portbuild/article.xml Mon Feb 11 23:21:09 2013 (r40952) @@ -217,13 +217,13 @@ be updated first unless -novcs is specified. It should be run as root: - &prompt.root; /var/portbuild/scripts/makeworld ${arch} ${branch} ${buildid} [-novcs] + &prompt.root; /a/portbuild/admin/scripts/makeworld ${arch} ${branch} ${buildid} [-novcs] The bindist.tar tarball is created from the previously installed world by the mkbindist script. It should be also be run as root: - &prompt.root; /var/portbuild/scripts/mkbindist ${arch} ${branch} ${buildid} + &prompt.root; /a/portbuild/admin/scripts/mkbindist ${arch} ${branch} ${buildid} The per-machine tarballs are located in ${arch}/clients. @@ -2090,10 +2090,15 @@ ssh_cmd="/usr/local/bin/ssh"HEAD. + + As + srcbuild: + + - Edit /var/portbuild/conf/server.conf + Edit /a/portbuild/conf/admin/admin.conf with the following changes: @@ -2118,7 +2123,7 @@ ssh_cmd="/usr/local/bin/ssh" - Run /var/portbuild/updatesnap manually. + Run /a/portbuild/admin/scripts/updatesnap manually. @@ -2126,24 +2131,21 @@ ssh_cmd="/usr/local/bin/ssh" Steps necessary after <application>qmanager</application> is started - - Again, as - portbuild: - - For each branch that will be supported, do the following: - Kick-start the build for the branch with: + As portbuild, + kick-start the build for the branch with: build create arch branch - Create + As srcbuild, + create bindist.tar. @@ -2160,7 +2162,7 @@ ssh_cmd="/usr/local/bin/ssh" - Edit /var/portbuild/conf/server.conf + Edit /a/portbuild/admin/conf/admin.conf with the following changes: @@ -2187,7 +2189,7 @@ zfs destroy -r a/snap/src-o You will probably find that the following files and - symlinks in /var/portbuild/errorlogs/ + symlinks in /a/portbuild/errorlogs/ can be removed: @@ -2232,7 +2234,7 @@ zfs destroy -r a/snap/src-o - Edit /var/portbuild/conf/server.conf + Edit /a/portbuild/admin/conf/admin.conf with the following changes: @@ -2247,7 +2249,7 @@ zfs destroy -r a/snap/src-o - Run /var/portbuild/updatesnap manually. + Run /a/portbuild/admin/scripts/updatesnap manually. @@ -2270,6 +2272,7 @@ zfs destroy -r a/snap/src-o Steps necessary before <application>qmanager</application> is started + The initial steps need to be done as root. @@ -2283,7 +2286,7 @@ zfs destroy -r a/snap/src-o - mkdir /var/portbuild/arch + mkdir /a/portbuild/arch @@ -2293,9 +2296,9 @@ zfs destroy -r a/snap/src-o - &prompt.root; chown portbuild:portbuild /var/portbuild/arch; -&prompt.root; chmod 775 /var/portbuild/arch; -&prompt.root; cd /var/portbuild/arch + &prompt.root; chown portbuild:portbuild /a/portbuild/arch; +&prompt.root; chmod 775 /a/portbuild/arch; +&prompt.root; cd /a/portbuild/arch @@ -2384,7 +2387,7 @@ zfs destroy -r a/snap/src-o Make a private configuration directory: - &prompt.root; mkdir /var/portbuild/conf/arch + &prompt.root; mkdir /a/portbuild/conf/arch @@ -2402,20 +2405,20 @@ zfs destroy -r a/snap/src-o Add arch to SUPPORTED_ARCHS in - /var/portbuild/conf/server.conf. + /a/portbuild/admin/conf/admin.conf. Add the arch directory to - /var/portbuild/scripts/zbackup and - /var/portbuild/scripts/zexpire. + /a/portbuild/admin/scripts/zbackup and + /a/portbuild/admin/scripts/zexpire. Add an appropriate arch entry for - /var/portbuild/scripts/dologs to the portbuild + /a/portbuild/scripts/dologs to the portbuild crontab. (This is a hack and should go away.) From owner-svn-doc-all@FreeBSD.ORG Mon Feb 11 23:41:17 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 587B6698; Mon, 11 Feb 2013 23:41:17 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 4B304769; Mon, 11 Feb 2013 23:41:17 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1BNfHYg093686; Mon, 11 Feb 2013 23:41:17 GMT (envelope-from linimon@svn.freebsd.org) Received: (from linimon@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1BNfHKH093685; Mon, 11 Feb 2013 23:41:17 GMT (envelope-from linimon@svn.freebsd.org) Message-Id: <201302112341.r1BNfHKH093685@svn.freebsd.org> From: Mark Linimon Date: Mon, 11 Feb 2013 23:41:17 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40953 - head/en_US.ISO8859-1/articles/portbuild X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 23:41:17 -0000 Author: linimon Date: Mon Feb 11 23:41:16 2013 New Revision: 40953 URL: http://svnweb.freebsd.org/changeset/doc/40953 Log: Remove some more lies from the first section. Modified: head/en_US.ISO8859-1/articles/portbuild/article.xml Modified: head/en_US.ISO8859-1/articles/portbuild/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/portbuild/article.xml Mon Feb 11 23:21:09 2013 (r40952) +++ head/en_US.ISO8859-1/articles/portbuild/article.xml Mon Feb 11 23:41:16 2013 (r40953) @@ -63,7 +63,7 @@ The codebase Most of the package building magic occurs under the - /var/portbuild directory. Unless + /a/portbuild directory. Unless otherwise specified, all paths will be relative to this location. ${arch} will be used to specify one of the package architectures @@ -81,11 +81,12 @@ for the alpha architecture. - The scripts that control all of this live in - /var/portbuild/scripts/. + The scripts that control all of this live in either + /a/portbuild/scripts/ or. + /a/portbuild/admin/scripts/. These are the checked-out copies from the Subversion repository at - - base/projects/portbuild/scripts/ + + base/projects/portbuild/ . Typically, incremental builds are done that use previous From owner-svn-doc-all@FreeBSD.ORG Tue Feb 12 02:14:16 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EE0FADE9; Tue, 12 Feb 2013 02:14:16 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-3.mit.edu (DMZ-MAILSEC-SCANNER-3.MIT.EDU [18.9.25.14]) by mx1.freebsd.org (Postfix) with ESMTP id 611B2CC8; Tue, 12 Feb 2013 02:14:16 +0000 (UTC) X-AuditID: 1209190e-b7f266d0000008cb-bb-5119a445fb45 Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) by dmz-mailsec-scanner-3.mit.edu (Symantec Messaging Gateway) with SMTP id A3.6E.02251.544A9115; Mon, 11 Feb 2013 21:09:09 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id r1C299qI028964; Mon, 11 Feb 2013 21:09:09 -0500 Received: from multics.mit.edu (SYSTEM-LOW-SIPB.MIT.EDU [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id r1C296gB012046 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 11 Feb 2013 21:09:08 -0500 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id r1C2959G018284; Mon, 11 Feb 2013 21:09:05 -0500 (EST) Date: Mon, 11 Feb 2013 21:09:05 -0500 (EST) From: Benjamin Kaduk To: Eitan Adler Subject: Re: svn commit: r40942 - head/en_US.ISO8859-1/books/arch-handbook/driverbasics In-Reply-To: <201302111346.r1BDkQXD012859@svn.freebsd.org> Message-ID: References: <201302111346.r1BDkQXD012859@svn.freebsd.org> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrAIsWRmVeSWpSXmKPExsUixG6nruu6RDLQoOeQvsWPj4eYLHb9ncNs cWPRfiaL3f29zA4sHjM+zWcJYIzisklJzcksSy3St0vgynhw37ngP0/F9puzWRoY13B1MXJy SAiYSCx9v4IFwhaTuHBvPVsXIxeHkMA+Rokzs2YzQTgbGSU2ddxhh3AOMUm0T/rACNIiJNDA KHHjXBmIzSKgLfGzvRNsFJuAisTMNxvZQGwRIPv7/p9MIDazQJTEnqWNrCC2sECkxL8Fm4GG cnBwClhJNB7UAAnzCjhILNnaxA4x3lJi1rz1YK2iAjoSq/dPYYGoEZQ4OfMJC8RIS4l/a3+x TmAUnIUkNQtJagEj0ypG2ZTcKt3cxMyc4tRk3eLkxLy81CJdY73czBK91JTSTYyggOWU5NvB +PWg0iFGAQ5GJR7eBlHJQCHWxLLiytxDjJIcTEqivP/mA4X4kvJTKjMSizPii0pzUosPMUpw MCuJ8C77KBEoxJuSWFmVWpQPk5LmYFES572SctNfSCA9sSQ1OzW1ILUIJivDwaEkweu1GGio YFFqempFWmZOCUKaiYMTZDgP0PBkkBre4oLE3OLMdIj8KUZFKXHeFJCEAEgiozQPrheWUF4x igO9IsxbAlLFA0xGcN2vgAYzAQ3mzBEHGVySiJCSamAM3VheM7PX0W/XIoUtKr1bG5TVK7Xn abaofn59P37KXz1Nv+Mz7lU/VZzWqdV565PX+4PRysqL4t8lOH3Suf71ROK3H8nfrvl3L1ur G2q5+XSgaNRvvsPzG7++3yDWmrp3Kue03shJwTnuE84Vrji1aukf3usmDvtKt+wMFbMRb/4j 7V6/tHK9EktxRqKhFnNRcSIAjaUisgMDAAA= Cc: svn-doc-head@freebsd.org, svn-doc-all@freebsd.org, doc-committers@freebsd.org X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Feb 2013 02:14:17 -0000 On Mon, 11 Feb 2013, Eitan Adler wrote: > > Modified: head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml > ============================================================================== > --- head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml Mon Feb 11 13:46:24 2013 (r40941) > +++ head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml Mon Feb 11 13:46:26 2013 (r40942) > @@ -135,17 +134,17 @@ DECLARE_MODULE(skeleton, skel_mod, SI_SU > > Makefile > > - FreeBSD provides a makefile include that you can use to > - quickly compile your kernel addition. > + FreeBSD provides a makefile include to > + quickly compile a kernel addition. This sentence does not seem right -- the user compiles the module, not the include file. I think these .mk files are referred to as "system makefiles", anyway. The best I can do on short notice is: "FreeBSD provides a system makefile to simplify compiling a kernel module." > SRCS=skeleton.c > KMOD=skeleton > > @@ -201,8 +200,8 @@ KMOD=skeleton > the source tree. > > This simple example pseudo-device remembers whatever values > - you write to it and can then supply them back to you when you > - read from it. > + that are written to it and can then echo them back when > + read. "whatever values that are written to it" doesn't seem right; "whatever values are written to it" feels much better. -Ben > > Example of a Sample Echo Pseudo-Device Driver for From owner-svn-doc-all@FreeBSD.ORG Tue Feb 12 03:20:48 2013 Return-Path: <owner-svn-doc-all@FreeBSD.ORG> Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DC8A99B7; Tue, 12 Feb 2013 03:20:48 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-2.mit.edu (DMZ-MAILSEC-SCANNER-2.MIT.EDU [18.9.25.13]) by mx1.freebsd.org (Postfix) with ESMTP id 53C9EF3D; Tue, 12 Feb 2013 03:20:48 +0000 (UTC) X-AuditID: 1209190d-b7fa66d0000008f6-10-5119b3dd060c Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) by dmz-mailsec-scanner-2.mit.edu (Symantec Messaging Gateway) with SMTP id 38.48.02294.DD3B9115; Mon, 11 Feb 2013 22:15:41 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id r1C3Fej9002655; Mon, 11 Feb 2013 22:15:40 -0500 Received: from multics.mit.edu (SYSTEM-LOW-SIPB.MIT.EDU [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id r1C3FcRP004571 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 11 Feb 2013 22:15:40 -0500 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id r1C3FcrH029599; Mon, 11 Feb 2013 22:15:38 -0500 (EST) Date: Mon, 11 Feb 2013 22:15:38 -0500 (EST) From: Benjamin Kaduk <kaduk@MIT.EDU> To: Dru Lavigne <dru@freebsd.org> Subject: Re: svn commit: r40946 - head/en_US.ISO8859-1/books/handbook/geom In-Reply-To: <201302111450.r1BEoXIR033682@svn.freebsd.org> Message-ID: <alpine.GSO.1.10.1302112114030.9389@multics.mit.edu> References: <201302111450.r1BEoXIR033682@svn.freebsd.org> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrAIsWRmVeSWpSXmKPExsUixG6nrnt3s2SgQdNNFosfHw8xWXQ1qVrc WLSfyWJ3fy+zA4vHjE/zWQIYo7hsUlJzMstSi/TtErgyrkxsZCx4bFmx/sw25gbGS7pdjJwc EgImEvuuf2OGsMUkLtxbz9bFyMUhJLCPUWL5ky9gCSGBjYwSt/+UQCQOMUm8W9TCDuE0MEpM 6n7F0sXIwcEioC1x8qcUSAObgIrEzDcb2UBsEQFFiadf9zKC2MwCURJ7ljaygtjCAl4Sv95O YwGxOQWsJP7dXQ0W5xVwkLiyZDsLxGJLiQsXdoH1igroSKzeP4UFokZQ4uTMJywQMy0l/q39 xTqBUXAWktQsJKkFjEyrGGVTcqt0cxMzc4pTk3WLkxPz8lKLdI30cjNL9FJTSjcxggKWU5J3 B+O7g0qHGAU4GJV4eBtEJQOFWBPLiitzDzFKcjApifJe3ggU4kvKT6nMSCzOiC8qzUktPsQo wcGsJMK77KNEoBBvSmJlVWpRPkxKmoNFSZz3SspNfyGB9MSS1OzU1ILUIpisDAeHkgTvtE1A QwWLUtNTK9Iyc0oQ0kwcnCDDeYCGPwWp4S0uSMwtzkyHyJ9iVJQS590MkhAASWSU5sH1whLK K0ZxoFeEeT+DVPEAkxFc9yugwUxAgzlzxEEGlyQipKQaGFdwmG/cNHPz3neZ32P2dW4wn6ao JVh6ser7Qd3T87TNzdMtLA3euO8tYPS/EnTsxrSrvJdfyMXvaOBOTK7SUJqerdvK21L2WatW 13jmnLRa3saDJotns82PnSD53K01rvhOtcUi0dLZAn6Bp9fNifo7t01v3/F5mZoM/yxF7bcW Lyn+mnC6VomlOCPRUIu5qDgRAMHIhG8DAwAA Cc: svn-doc-head@freebsd.org, svn-doc-all@freebsd.org, doc-committers@freebsd.org X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" <svn-doc-all.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-all> List-Post: <mailto:svn-doc-all@freebsd.org> List-Help: <mailto:svn-doc-all-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 12 Feb 2013 03:20:48 -0000 On Mon, 11 Feb 2013, Dru Lavigne wrote: > Author: dru > Date: Mon Feb 11 14:50:33 2013 > New Revision: 40946 > URL: http://svnweb.freebsd.org/changeset/doc/40946 > > Log: > This patch addresses the following: > > - fixes xref tags > > - some tightening and removing of redundancy > > - fixed some confusion in glabel section > > Approved by gjb (mentor) > > Modified: > head/en_US.ISO8859-1/books/handbook/geom/chapter.xml > > Modified: head/en_US.ISO8859-1/books/handbook/geom/chapter.xml > ============================================================================== > --- head/en_US.ISO8859-1/books/handbook/geom/chapter.xml Mon Feb 11 13:47:43 2013 (r40945) > +++ head/en_US.ISO8859-1/books/handbook/geom/chapter.xml Mon Feb 11 14:50:33 2013 (r40946) > @@ -35,11 +35,11 @@ > control utilities which use the framework for configuration. > This chapter will not go into in depth discussion on how GEOM > handles or controls I/O, the underlying subsystem, or code. > - This information is provided through the &man.geom.4; manual > - page and its various SEE ALSO references. This chapter is also > - not a definitive guide to <acronym>RAID</acronym> > - configurations. Only GEOM-supported <acronym>RAID</acronym> > - classifications will be discussed.</para> > + This information is provided in &man.geom.4; and its various If memory serves, we are using (all over the place, not just here) man page entities to refer to both the man page and the program itself. That is potentially a source of confusion, though not necessarily something to tackle here. > + <literal>SEE ALSO</literal> references. This chapter is also > + not a definitive guide to <acronym>RAID</acronym> configurations > + and only GEOM-supported <acronym>RAID</acronym> classifications > + will be discussed.</para> > > <para>After reading this chapter, you will know:</para> > > @@ -317,28 +316,28 @@ Done.</screen> > used to replace the old single disk.</para> > > <para>&man.gmirror.8; requires a kernel module, > - <filename>geom_mirror.ko</filename>, either built into the > - kernel or loaded at boot- or run-time. Manually load the > - kernel module now:</para> > + <filename>geom_mirror.ko</filename>, either compiled into a > + custom kernel or loaded at boot- or run-time. To manually > + load the kernel module now:</para> > > <screen>&prompt.root; <userinput>gmirror load</userinput></screen> > > - <para>Create the mirror with the two new drives.</para> > + <para>To create the mirror with the two new drives.</para> This should end with a colon, not a full stop? > @@ -384,8 +383,8 @@ Done.</screen> > &prompt.root; <userinput>newfs -U /dev/mirror/gm0s1e</userinput> > &prompt.root; <userinput>newfs -U /dev/mirror/gm0s1f</userinput></screen> > > - <para>Filesystems from the original disk > - (<devicename>ada0</devicename>) can now be copied onto the > + <para>Filesystems from the original I'm pretty sure Kirk and Bruce et all prefer "File systems" with a space, but it seems the NFSv4 guys are not having any of it (http://www.ietf.org/mail-archive/web/nfsv4/current/msg11661.html). > + <devicename>ada0</devicename> disk can now be copied onto the > mirror with &man.dump.8; and &man.restore.8;.</para> > > <screen>&prompt.root; <userinput>mount /dev/mirror/gm0s1a /mnt</userinput> > @@ -527,8 +526,8 @@ BSD 8 > 6 freebsd-ufs 130023424 838860800 > 7 freebsd-ufs 968884224 984640881</screen> > > - <para>If the whole disk was used in the output of &man.gpart.8; > - <command>show</command>, the capacity in these partition > + <para>If the whole disk shows as used in the output of > + <command>gpart show</command>, the capacity in these partition (Warren's suggestion seems fine.) > tables must be reduced by one sector. Edit the two files, > reducing the size of both the slice and last partition by one. > These are the last numbers in each listing.</para> > @@ -1010,8 +1000,8 @@ Done.</screen> > > <programlisting>192.168.1.0/24 RW /dev/da0s4d</programlisting> > > - <para>It will allow all hosts inside the private network access > - the file system on the <devicename>da0s4d</devicename> > + <para>This allows all hosts inside the specified private network > + access to the file system on the <devicename>da0s4d</devicename> I think it would be "gives X access to" or "allows X to access", not "allows X access to" > partition.</para> > > <para>To export this device, ensure it is not currently mounted, > @@ -1258,9 +1236,9 @@ ufsid/486b6fc16926168e N/A ad4s1f</ > /dev/ufsid/486b6fc16926168e /usr ufs rw 2 2</programlisting> > > <para>Any partitions with <literal>ufsid</literal> labels can be > - mounted in this way, eliminating the need to create permanent > - labels for them manually, while still enjoying the benefits of > - device-name independent mounting.</para> > + mounted in this way, eliminating the need to manually create > + permanent labels, while still enjoying the benefits of device > + name independent mounting.</para> I would put hyphens in here, but I tend to overuse hyphens in such cases. > </sect2> > </sect1> > > @@ -1332,12 +1309,11 @@ ufsid/486b6fc16926168e N/A ad4s1f</ > > <screen>&prompt.root; <userinput>newfs -O 2 -J /dev/da4.journal</userinput></screen> > > - <para>The previously issued command will create a > - <acronym>UFS</acronym>2 file system on the journaled > - device.</para> > + <para>This command will creates a <acronym>UFS</acronym>2 file > + system on the journaled device.</para> > > - <para>Effectively <command>mount</command> the device at the > - desired point with:</para> > + <para><command>mount</command> the device at the desired point Should this be "desired point" or "desired mount point"? > + with:</para> > > <screen>&prompt.root; <userinput>mount /dev/da4.journal <replaceable>/mnt</replaceable></userinput></screen> > > @@ -1351,21 +1327,21 @@ ufsid/486b6fc16926168e N/A ad4s1f</ > + <para>For better performance, the journal may be kept on another > + disk. In this configuration, the journal provider or storage > + device should be listed after the device to enable journaling > + on. Journaling may also be enabled on current file systems by This sentence is pretty confusing. Perhaps "the provider or storage device dedicated to holding the journal itself should be listed after the device whose transactions will be logged in the journal."? Still a bit unwieldly, it seems.... > + using <command>tunefs</command>. However, I'm not sure what "current file systems" are. Are they ones that are mounted, or just an already extant filesystem? Thanks for all the updates. -Ben > + <emphasis>always</emphasis> make a backup before attempting to > + alter a file system. In most cases, <command>gjournal</command> > + will fail if it is unable to create the journal, but this does > + not protect against data loss incurred as a result of misusing > <command>tunefs</command>.</para> From owner-svn-doc-all@FreeBSD.ORG Tue Feb 12 03:28:19 2013 Return-Path: <owner-svn-doc-all@FreeBSD.ORG> Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id CCDE7A50; Tue, 12 Feb 2013 03:28:19 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id A6B27F61; Tue, 12 Feb 2013 03:28:19 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1C3SJfq061757; Tue, 12 Feb 2013 03:28:19 GMT (envelope-from linimon@svn.freebsd.org) Received: (from linimon@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1C3SJDc061756; Tue, 12 Feb 2013 03:28:19 GMT (envelope-from linimon@svn.freebsd.org) Message-Id: <201302120328.r1C3SJDc061756@svn.freebsd.org> From: Mark Linimon <linimon@FreeBSD.org> Date: Tue, 12 Feb 2013 03:28:19 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40954 - head/en_US.ISO8859-1/articles/portbuild X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" <svn-doc-all.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-all> List-Post: <mailto:svn-doc-all@freebsd.org> List-Help: <mailto:svn-doc-all-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 12 Feb 2013 03:28:19 -0000 Author: linimon Date: Tue Feb 12 03:28:19 2013 New Revision: 40954 URL: http://svnweb.freebsd.org/changeset/doc/40954 Log: Collapse all the manual steps of "new architecture" into the addarch script. Modified: head/en_US.ISO8859-1/articles/portbuild/article.xml Modified: head/en_US.ISO8859-1/articles/portbuild/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/portbuild/article.xml Mon Feb 11 23:41:16 2013 (r40953) +++ head/en_US.ISO8859-1/articles/portbuild/article.xml Tue Feb 12 03:28:19 2013 (r40954) @@ -2273,51 +2273,25 @@ zfs destroy -r a/snap/src-<replaceable>o <sect2 id="new-arch-pre-qmanager"> <title>Steps necessary before <application>qmanager</application> is started - - The initial steps need to be done as - root. + The next steps are most easily done as user + portbuild. - - - If it has not already been done, create the - portbuild - user and group. - - - - mkdir /a/portbuild/arch - - - - Create a new zfs filesystem: - - &prompt.root; zfs create -o mountpoint=/a/portbuild/arch a/portbuild/arch - - - - &prompt.root; chown portbuild:portbuild /a/portbuild/arch; -&prompt.root; chmod 775 /a/portbuild/arch; -&prompt.root; cd /a/portbuild/arch - - - - Create the .ssh directory. - - - - The next steps are most easily done as user - portbuild. + The following assumes you have already run + mkportbuild. - Create an archive directory for buildlogs and errorlogs - under archive/. + As the portbuild user, run + + &prompt.user; /a/portbuild/admin/tools/addarch arch + + For each branch that will be supported, do the following: @@ -2361,8 +2335,10 @@ zfs destroy -r a/snap/src-o - Create a fresh portbuild.conf file - from one of the ones for another architecture. + Edit portbuild.conf + from one of the ones for another architecture. + addarch will have created a default + one for you. @@ -2372,16 +2348,6 @@ zfs destroy -r a/snap/src-o - &prompt.root; cd .ssh && ssh-keygen - - - - If desired, - edit the .ssh/config file for - convenience in using ssh. - - - If you need to create any tunnels: @@ -2400,7 +2366,7 @@ zfs destroy -r a/snap/src-o - Once again as root: + As srcbuild: @@ -2411,14 +2377,14 @@ zfs destroy -r a/snap/src-o Add the arch directory to - /a/portbuild/admin/scripts/zbackup and - /a/portbuild/admin/scripts/zexpire. + /a/portbuild/admin/scripts/zbackup. + (This is a hack and should go away.) - Add an appropriate arch entry for + Enable the appropriate arch entry for /a/portbuild/scripts/dologs to the portbuild crontab. (This is a hack and should go away.) @@ -2429,17 +2395,11 @@ zfs destroy -r a/snap/src-o Steps necessary after <application>qmanager</application> is started - Again as root: + Again as srcbuild: - Tell qmanager about the arch: - - python path/qmanager/qclient add_acl name=ports-arch uidlist=ports-arch gidlist=portbuild sense=1 - - - For each branch that will be supported, do the following: From owner-svn-doc-all@FreeBSD.ORG Tue Feb 12 04:01:58 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 6D9F1EB6 for ; Tue, 12 Feb 2013 04:01:58 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by mx1.freebsd.org (Postfix) with ESMTP id 469C610B for ; Tue, 12 Feb 2013 04:01:57 +0000 (UTC) Received: by mail-da0-f44.google.com with SMTP id z20so3080716dae.17 for ; Mon, 11 Feb 2013 20:01:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=3S+doceiQ3gRJaSFf/7jkF0QX+zwt5yK/ndDDUu4OsI=; b=QOD9BGq1AgTpl9CjZmuwInQJ4/l9B2XipuCPoTMpZBDp7uS+022iBcwfrzg87mnTVa 1mTGKzDT63fSweGTHQDogs0KBG54fK0QMu3xVZlP6W07tWdgtNjwlQ4dR11DDkQInVMP OMpQXmCDnh/D4Ngf5cIuNdB4IZydCqfgAwEt4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :x-gm-message-state; bh=3S+doceiQ3gRJaSFf/7jkF0QX+zwt5yK/ndDDUu4OsI=; b=Mz7vvuJhC4qE6goUT2V50IfSuSPYBfgK7JjaofbLVafC3VR/rK0O7r0aPi2TFrF3ji VOShSS5HGAM+/VESaHULgBEOmnJYU0pdZLo2kp4J6q7LgvcR0WeuJ/h2uIROpUS6ZGRw B9ThirtqKFScRjs3H4oUqAQ/W0UQzFREuXYAAwbRhyghqgMrLpTaftNazE2D2/NHI1jQ JH2OYlPOYaDIL8oGFkvlm/u5UeYO8fsxHPnaMkRIEgyNGxnbq9GctqRVXotVw0or6FC4 5PnzEWGC4RCEqzcCNKHN6EgyZe1twotHhUvMMz7upnd6d48WDHqscxe+19VekD90h007 SVHQ== X-Received: by 10.66.76.42 with SMTP id h10mr47862051paw.59.1360641717363; Mon, 11 Feb 2013 20:01:57 -0800 (PST) MIME-Version: 1.0 Sender: lists@eitanadler.com Received: by 10.66.148.10 with HTTP; Mon, 11 Feb 2013 20:01:27 -0800 (PST) In-Reply-To: References: <201302111450.r1BEoXIR033682@svn.freebsd.org> From: Eitan Adler Date: Mon, 11 Feb 2013 23:01:27 -0500 X-Google-Sender-Auth: IRciJ-1N8h6mlRfnvwSKvkVAHuU Message-ID: Subject: Re: svn commit: r40946 - head/en_US.ISO8859-1/books/handbook/geom To: Benjamin Kaduk Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQmr15eeXeELqeFW6CsyD0ipcxuABHv0+hiJ6Q8123kFzWofvJ+bIJiMfqqRzX9xtLYuxhJk Cc: svn-doc-head@freebsd.org, Dru Lavigne , svn-doc-all@freebsd.org, doc-committers@freebsd.org X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Feb 2013 04:01:58 -0000 On 11 February 2013 22:15, Benjamin Kaduk wrote: > I'm pretty sure Kirk and Bruce et all prefer "File systems" with a space, > but it seems the NFSv4 guys are not having any of it > (http://www.ietf.org/mail-archive/web/nfsv4/current/msg11661.html). http://www.freebsd.org/doc/en/books/fdp-primer/writing-style-word-list.html We spell it with a space. From owner-svn-doc-all@FreeBSD.ORG Tue Feb 12 05:36:27 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EB21B9C2; Tue, 12 Feb 2013 05:36:27 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-4.mit.edu (DMZ-MAILSEC-SCANNER-4.MIT.EDU [18.9.25.15]) by mx1.freebsd.org (Postfix) with ESMTP id 4EDA633A; Tue, 12 Feb 2013 05:36:27 +0000 (UTC) X-AuditID: 1209190f-b7f586d000000915-0f-5119d3a8ab6a Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) by dmz-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id C5.6F.02325.8A3D9115; Tue, 12 Feb 2013 00:31:20 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id r1C5VKAb014462; Tue, 12 Feb 2013 00:31:20 -0500 Received: from multics.mit.edu (SYSTEM-LOW-SIPB.MIT.EDU [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id r1C5VIg2016448 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 12 Feb 2013 00:31:19 -0500 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id r1C5VHHK020441; Tue, 12 Feb 2013 00:31:17 -0500 (EST) Date: Tue, 12 Feb 2013 00:31:17 -0500 (EST) From: Benjamin Kaduk To: Dru Lavigne Subject: Re: svn commit: r40947 - head/en_US.ISO8859-1/books/handbook/filesystems In-Reply-To: <201302111458.r1BEwYW7034821@svn.freebsd.org> Message-ID: References: <201302111458.r1BEwYW7034821@svn.freebsd.org> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPIsWRmVeSWpSXmKPExsUixG6nrrvismSgwe3VIhY/Ph5isuhqUrW4 sWg/k8Xu/l5mBxaPGZ/mswQwRnHZpKTmZJalFunbJXBlXHzziqVgn2DFip4HjA2MTXxdjJwc EgImEjseH2aFsMUkLtxbz9bFyMUhJLCPUWLJt0esEM5GRomdD2azQDiHmCTufZgMlWlglOja fom9i5GDg0VAW+L42jyQUWwCKhIz32xkA7FFBBQlnn7dywhiMwtESexZ2gi2TlggWOJX9wqw Vk4BK4nXJw1BTF4BB4mPV2RAKoQELCV6rv0C6xQV0JFYvX8KC4jNKyAocXLmExaIiZYS/9b+ Yp3AKDgLSWoWktQCRqZVjLIpuVW6uYmZOcWpybrFyYl5ealFuiZ6uZkleqkppZsYQeHKKcm/ g/HbQaVDjAIcjEo8vA2ikoFCrIllxZW5hxglOZiURHmLzgOF+JLyUyozEosz4otKc1KLDzFK cDArifAu+ygRKMSbklhZlVqUD5OS5mBREue9mnLTX0ggPbEkNTs1tSC1CCYrw8GhJME74RLQ UMGi1PTUirTMnBKENBMHJ8hwHqDh10BqeIsLEnOLM9Mh8qcYFaXEeVeDJARAEhmleXC9sHTy ilEc6BVh3qUgVTzAVATX/QpoMBPQYM4ccZDBJYkIKakGRtUHz/qvu/l2iwksc+CUES8oaZg0 NXBR415nB161zbePGYoJn7pZsujnuyaxQ8vK1UM61RP037h9usy4+80Vxkt3/sa/ND4V8j1+ o4pt3OrNQvYmfwWCf8quuv/uuxjnX75XydMlvx79sOqN9WOhnKiPtX3NgY4cBt6qjiFbpqhI 93EK+yxnVGIpzkg01GIuKk4EAPRGsM0CAwAA Cc: svn-doc-head@freebsd.org, svn-doc-all@freebsd.org, doc-committers@freebsd.org X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Feb 2013 05:36:28 -0000 On Mon, 11 Feb 2013, Dru Lavigne wrote: > Modified: > head/en_US.ISO8859-1/books/handbook/filesystems/chapter.xml > > Modified: head/en_US.ISO8859-1/books/handbook/filesystems/chapter.xml > ============================================================================== > --- head/en_US.ISO8859-1/books/handbook/filesystems/chapter.xml Mon Feb 11 14:50:33 2013 (r40946) > +++ head/en_US.ISO8859-1/books/handbook/filesystems/chapter.xml Mon Feb 11 14:58:34 2013 (r40947) > @@ -27,32 +27,30 @@ > + They allow users to upload and store files, provide access > + to data, and make hard drives useful. Different operating > + systems differ in their native file system. Traditionally, the > + native &os; file system has been the Unix File System > + UFS which has been recently modernized as > + UFS2. Since &os; 7.0, the Z File UFS2 is recent only in a very relative sense -- I used it (for non-root filesystems, I suppose) when I first picked up FreeBSD 5.2 in 2004. We can probably just say "which has been modernized as UFS2" at this point. > + System ZFS is also available as a native file > system. > > @@ -529,37 +509,34 @@ errors: No known data errors > > Data Verification > > - As previously mentioned, ZFS uses > + ZFS uses > checksums to verify the integrity of Hmm, checksums probably doesn't need markup, here. > - stored data. They are enabled automatically upon creation > + stored data. These are enabled automatically upon creation > of file systems and may be disabled using the following > command: > > @@ -571,43 +548,39 @@ config: > + ZFS supports different types of quotas: the refquota, > + the general quota, the user quota, and the group quota. > + This section explains the basics of each type and includes > + some usage instructions. Grammar is pretty lousy in this section, but you were just reformatting so I'll skip the details. Some things to look at for the next pass, I guess. -Ben From owner-svn-doc-all@FreeBSD.ORG Tue Feb 12 09:14:36 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 45ED3A87; Tue, 12 Feb 2013 09:14:36 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 29A7EEEB; Tue, 12 Feb 2013 09:14:36 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1C9EajJ065123; Tue, 12 Feb 2013 09:14:36 GMT (envelope-from ryusuke@svn.freebsd.org) Received: (from ryusuke@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1C9EaBm065122; Tue, 12 Feb 2013 09:14:36 GMT (envelope-from ryusuke@svn.freebsd.org) Message-Id: <201302120914.r1C9EaBm065122@svn.freebsd.org> From: Ryusuke SUZUKI Date: Tue, 12 Feb 2013 09:14:35 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40955 - head/ja_JP.eucJP/books/handbook/cutting-edge X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Feb 2013 09:14:36 -0000 Author: ryusuke Date: Tue Feb 12 09:14:35 2013 New Revision: 40955 URL: http://svnweb.freebsd.org/changeset/doc/40955 Log: Refine translation. Modified: head/ja_JP.eucJP/books/handbook/cutting-edge/chapter.xml Modified: head/ja_JP.eucJP/books/handbook/cutting-edge/chapter.xml ============================================================================== --- head/ja_JP.eucJP/books/handbook/cutting-edge/chapter.xml Tue Feb 12 03:28:19 2013 (r40954) +++ head/ja_JP.eucJP/books/handbook/cutting-edge/chapter.xml Tue Feb 12 09:14:35 2013 (r40955) @@ -147,7 +147,7 @@ ソースコードにパッチを当て、コードからバイナリを再構築し、 バイナリを再びインストールする必要がありました。 - 現在では &os; に freebsd-update + 現在の &os; では freebsd-update と呼ばれるユーティリティが追加され、状況は変わりました。 このユーティリティは 2 つの機能を持っています。 第一に、&os; ベースシステムのビルドやインストールを行うことなく、 @@ -283,8 +283,8 @@ MergeChanges /etc/ /var/named/etc/root 宛てにメールで通知されます。 + ダウンロードされたパッチを手動でインストールする必要があり、 + このことは root 宛てにメールで通知されます。 うまく行かなかった場合には、freebsd-update を以下のように実行すると、最後の変更までロールバックできます。 @@ -661,20 +661,20 @@ before running "/usr/sbin/freebsd-update security/snort のような侵入検知システムの置き換えになるものではありません。 freebsd-update はデータをディスクに保存するので、 - 明らかに不正な変更が行われる可能性があります。 - この不正な変更の可能性は、 + 不正な変更が行われる可能性があります。 kern.securelevel の設定と、 freebsd-update のデータを使用しないときに、 - 読み取りのみの許可属性に設定されているファイルシステムに置くことで低くすることができますが、 + 読み取りのみの許可属性に設定されているファイルシステムに置くことで、 + 不正な変更の可能性を低くできますが、 よりよい解決方法は、 DVD または安全に保存されている外部 USB ディスクのような安全なディスクとシステムを比較することです。 - これで、システムは検査されます。そして、 + このコマンドを実行すると、システムは検査され、 リリースファイルの &man.sha256.1; - ハッシュ値と現在インストールされているファイルの値がファイルの一覧と共に表示されます。 + ハッシュ値と現在インストールされているファイルのハッシュ値がファイルの一覧と共に表示されます。 これが outfile.ids ファイルに出力する理由です。 目で比較するにはとても早くスクロールし、 コンソールバッファをいっぱいに満たしてしまいます。 From owner-svn-doc-all@FreeBSD.ORG Tue Feb 12 09:42:25 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3AF96ED; Tue, 12 Feb 2013 09:42:25 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 231C6C3; Tue, 12 Feb 2013 09:42:25 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1C9gOcN073457; Tue, 12 Feb 2013 09:42:24 GMT (envelope-from ryusuke@svn.freebsd.org) Received: (from ryusuke@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1C9gOE0073456; Tue, 12 Feb 2013 09:42:24 GMT (envelope-from ryusuke@svn.freebsd.org) Message-Id: <201302120942.r1C9gOE0073456@svn.freebsd.org> From: Ryusuke SUZUKI Date: Tue, 12 Feb 2013 09:42:24 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40956 - head/ja_JP.eucJP/htdocs/internal X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Feb 2013 09:42:25 -0000 Author: ryusuke Date: Tue Feb 12 09:42:23 2013 New Revision: 40956 URL: http://svnweb.freebsd.org/changeset/doc/40956 Log: - Merge the following from the English version: r39593 -> r40940 head/ja_JP.eucJP/htdocs/internal/internal.xml Modified: head/ja_JP.eucJP/htdocs/internal/internal.xml Modified: head/ja_JP.eucJP/htdocs/internal/internal.xml ============================================================================== --- head/ja_JP.eucJP/htdocs/internal/internal.xml Tue Feb 12 09:14:35 2013 (r40955) +++ head/ja_JP.eucJP/htdocs/internal/internal.xml Tue Feb 12 09:42:23 2013 (r40956) @@ -4,7 +4,7 @@ ]> - + @@ -47,10 +47,6 @@ package ビルドプロセス について。

-

FreeBSD.org にある - 個人のホームページ と - イベントの写真。

-

コアチームによる Hat Term Limits Policy や、&a.imp; によるガイドラインが how to work with hats にあります。

From owner-svn-doc-all@FreeBSD.ORG Tue Feb 12 14:40:47 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DF946741; Tue, 12 Feb 2013 14:40:47 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id D180187E; Tue, 12 Feb 2013 14:40:47 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1CEel7Q065502; Tue, 12 Feb 2013 14:40:47 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1CEelue065501; Tue, 12 Feb 2013 14:40:47 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201302121440.r1CEelue065501@svn.freebsd.org> From: Dru Lavigne Date: Tue, 12 Feb 2013 14:40:47 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40957 - head/en_US.ISO8859-1/books/handbook/mail X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Feb 2013 14:40:47 -0000 Author: dru Date: Tue Feb 12 14:40:47 2013 New Revision: 40957 URL: http://svnweb.freebsd.org/changeset/doc/40957 Log: White space fix only. Translators can ignore. Approved by: gjb (mentor) Modified: head/en_US.ISO8859-1/books/handbook/mail/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/mail/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/mail/chapter.xml Tue Feb 12 09:42:23 2013 (r40956) +++ head/en_US.ISO8859-1/books/handbook/mail/chapter.xml Tue Feb 12 14:40:47 2013 (r40957) @@ -28,43 +28,46 @@ Synopsis + email - Electronic Mail, better known as email, is one of the - most widely used forms of communication today. This chapter provides - a basic introduction to running a mail server on &os;, as well as an - introduction to sending and receiving email using &os;; however, - it is not a complete reference and in fact many important - considerations are omitted. For more complete coverage of the - subject, the reader is referred to the many excellent books listed - in . + Electronic Mail, better known as email, is + one of the most widely used forms of communication today. + This chapter provides a basic introduction to running a mail + server on &os;, as well as an introduction to sending and + receiving email using &os;; however, it is not a complete + reference and in fact many important considerations are omitted. + For more complete coverage of the subject, the reader is + referred to the many excellent books listed in + . After reading this chapter, you will know: - What software components are involved in sending and receiving - electronic mail. + What software components are involved in sending and + receiving electronic mail. - Where basic sendmail configuration - files are located in FreeBSD. + Where basic sendmail + configuration files are located in FreeBSD. - The difference between remote and + The difference between remote and local mailboxes. - How to block spammers from illegally using your mail server as a - relay. + How to block spammers from illegally using your mail + server as a relay. - How to install and configure an alternate Mail Transfer Agent on - your system, replacing sendmail. + How to install and configure an alternate Mail Transfer + Agent on your system, replacing + sendmail. @@ -84,22 +87,24 @@ - How to configure SMTP Authentication for added security. + How to configure SMTP Authentication for added + security. - How to install and use a Mail User Agent, such as - mutt to send and receive email. + How to install and use a Mail User Agent, such as + mutt to send and receive + email. - - How to download your mail from a remote POP - or IMAP server. + How to download your mail from a remote + POP or IMAP + server. - How to automatically apply filters and rules to incoming + How to automatically apply filters and rules to incoming email. @@ -119,56 +124,61 @@ Know how to install additional third-party software - (). + (). + Using Electronic Mail + POP IMAP DNS - There are five major parts involved in an email exchange. They - are: the user program, the server daemon, DNS, a - remote or local mailbox, and of course, the - mailhost itself. + There are five major parts involved in an email exchange. + They are: the user program, + the server daemon, DNS, a + remote or local mailbox, and of course, the mailhost itself. The User Program This includes command line programs such as mutt, - alpine, elm, - and mail, and GUI programs such as - balsa, + alpine, + elm, and + mail, and GUI + programs such as balsa, xfmail to name a few, and something more sophisticated like a WWW browser. These programs simply pass off the email transactions to the local - mailhost, either - by calling one of the server - daemons available, or delivering it over TCP. - + mailhost, + either by calling one of the server + daemons available, or delivering it over + TCP. + Mailhost Server Daemon + - mail server daemons - sendmail + mail server daemons + sendmail - mail server daemons - postfix + mail server daemons + postfix - mail server daemons - qmail + mail server daemons + qmail - mail server daemons - exim + mail server daemons + exim &os; ships with sendmail by @@ -189,14 +199,15 @@ - The server daemon usually has two functions—it is responsible - for receiving incoming mail as well as delivering outgoing mail. It is - not responsible for the collection of mail using protocols - such as POP or IMAP to - read your email, nor does it allow connecting to local - mbox or Maildir mailboxes. You may require - an additional daemon for - that. + The server daemon usually has two functions—it is + responsible for receiving incoming mail as well as delivering + outgoing mail. It is not responsible + for the collection of mail using protocols such as + POP or IMAP to read + your email, nor does it allow connecting to local + mbox or Maildir mailboxes. You may + require an additional daemon for that. Older versions of sendmail @@ -205,7 +216,7 @@ Make sure that you are running a current version to avoid these problems. Optionally, install an alternative MTA from the &os; - Ports Collection. + Ports Collection. @@ -213,12 +224,12 @@ Email and DNS The Domain Name System (DNS) and its daemon - named play a large role in the delivery of - email. In order to deliver mail from your site to another, the - server daemon will look up the remote site in the DNS to determine the - host that will receive mail for the destination. This process - also occurs when mail is sent from a remote host to your mail - server. + named play a large role in the delivery + of email. In order to deliver mail from your site to another, + the server daemon will look up the remote site in the DNS + to determine the host that will receive mail for the + destination. This process also occurs when mail is sent from + a remote host to your mail server. MX record @@ -242,149 +253,154 @@ FreeBSD.org mail is handled (pri=10) by Receiving Mail + - email - receiving + email + receiving - Receiving mail for your domain is done by the mail host. It - will collect all mail sent to your domain and store it - either in mbox (the default method for storing mail) or Maildir format, depending - on your configuration. - Once mail has been stored, it may either be read locally using - applications such as &man.mail.1; or + Receiving mail for your domain is done by the mail host. + It will collect all mail sent to your domain and store it + either in mbox (the default method for + storing mail) or Maildir format, depending on your + configuration. Once mail has been stored, it may either be + read locally using applications such as &man.mail.1; or mutt, or remotely accessed and - collected using protocols such as - POP or IMAP. - This means that should you only - wish to read mail locally, you are not required to install a - POP or IMAP server. + collected using protocols such as POP or + IMAP. This means that should you only + wish to read mail locally, you are not required to install + a POP or IMAP + server. - Accessing remote mailboxes using <acronym>POP</acronym> and <acronym>IMAP</acronym> + Accessing remote mailboxes using <acronym>POP</acronym> + and <acronym>IMAP</acronym> - POP - IMAP - In order to access mailboxes remotely, you are required to - have access to a POP or IMAP - server. These protocols allow users to connect to their mailboxes from - remote locations with ease. Though both - POP and IMAP allow users - to remotely access mailboxes, IMAP offers - many advantages, some of which are: - - - - IMAP can store messages on a remote - server as well as fetch them. - - - - IMAP supports concurrent updates. - + POP + IMAP + In order to access mailboxes remotely, you are required + to have access to a POP or + IMAP server. These protocols allow users + to connect to their mailboxes from remote locations with + ease. Though both POP and + IMAP allow users to remotely access + mailboxes, IMAP offers many advantages, + some of which are: + + + + IMAP can store messages on a + remote server as well as fetch them. + + + + IMAP supports concurrent + updates. + - + IMAP can be extremely useful over - low-speed links as it allows users to fetch the structure - of messages without downloading them; it can also - perform tasks such as searching on the server in + low-speed links as it allows users to fetch the + structure of messages without downloading them; it can + also perform tasks such as searching on the server in order to minimize data transfer between clients and servers. - + - + - In order to install a POP or - IMAP server, the following steps should be - performed: + In order to install a POP or + IMAP server, the following steps should + be performed: - + Choose an IMAP or - POP server that best suits your needs. - The following POP and + POP server that best suits your + needs. The following POP and IMAP servers are well known and serve as some good examples: - - - qpopper; - - - - teapop; - - - - imap-uw; - - - - courier-imap; - - - - dovecot; - - + + + qpopper; + + + + teapop; + + + + imap-uw; + + + + courier-imap; + + + + dovecot; + + - + Install the POP or - IMAP daemon of your choosing from the - ports - collection. + IMAP daemon of your choosing from + the ports collection. - Where required, modify /etc/inetd.conf - to load the POP or - IMAP server. + Where required, modify + /etc/inetd.conf to load the + POP or IMAP + server. - + - It should be noted that both POP and - IMAP transmit information, including - username and password credentials in clear-text. This means - that if you wish to secure the transmission of information - across these protocols, you should consider tunneling - sessions over &man.ssh.1; or using SSL. Tunneling sessions is - described in and SSL is + It should be noted that both POP + and IMAP transmit information, + including username and password credentials in clear-text. + This means that if you wish to secure the transmission + of information across these protocols, you should consider + tunneling sessions over &man.ssh.1; or using SSL. + Tunneling sessions is described in + and SSL is described in . - + - Accessing Local Mailboxes + Accessing Local Mailboxes Mailboxes may be accessed locally by directly utilizing MUAs on the server on which the mailbox resides. This can be done using applications such as - mutt or &man.mail.1;. - + mutt or &man.mail.1;. The Mail Host + mail host The mail host is the name given to a server that is - responsible for delivering and receiving mail for your host, and - possibly your network. + responsible for delivering and receiving mail for your host, + and possibly your network. - - Christopher - Shumway - Contributed by - + + Christopher + Shumway + Contributed by + <application>sendmail</application> Configuration @@ -393,13 +409,13 @@ FreeBSD.org mail is handled (pri=10) by sendmail - &man.sendmail.8; is the default Mail Transfer Agent (MTA) in - FreeBSD. sendmail's job is to accept - mail from Mail User Agents (MUA) and deliver it - to the appropriate mailer as defined by its configuration file. - sendmail can also accept network - connections and deliver mail to local mailboxes or deliver it to - another program. + &man.sendmail.8; is the default Mail Transfer Agent (MTA) + in FreeBSD. sendmail's job is to + accept mail from Mail User Agents (MUA) and + deliver it to the appropriate mailer as defined by its + configuration file. sendmail can + also accept network connections and deliver mail to local + mailboxes or deliver it to another program. sendmail uses the following configuration files: @@ -436,157 +452,161 @@ FreeBSD.org mail is handled (pri=10) by - /etc/mail/access - + /etc/mail/access sendmail access database - file + file + - /etc/mail/aliases - + /etc/mail/aliases Mailbox aliases + - /etc/mail/local-host-names - + /etc/mail/local-host-names Lists of hosts sendmail - accepts mail for - + accepts mail for + + - /etc/mail/mailer.conf - + /etc/mail/mailer.conf Mailer program configuration + - /etc/mail/mailertable - + /etc/mail/mailertable Mailer delivery table + - /etc/mail/sendmail.cf - + /etc/mail/sendmail.cf sendmail master - configuration file + configuration file + - /etc/mail/virtusertable - + /etc/mail/virtusertable Virtual users and domain tables - - <filename>/etc/mail/access</filename> + + <filename>/etc/mail/access</filename> - The access database defines what host(s) or IP addresses - have access to the local mail server and what kind of access - they have. Hosts can be listed as , - , or simply passed - to sendmail's error handling routine with a given mailer error. - Hosts that are listed as , which is the - default, are allowed to send mail to this host as long as the - mail's final destination is the local machine. Hosts that are - listed as are rejected for all mail - connections. Hosts that have the option - for their hostname are allowed to send mail for any destination - through this mail server. + The access database defines what host(s) or IP addresses + have access to the local mail server and what kind of access + they have. Hosts can be listed as , + , or simply + passed to sendmail's error + handling routine with a given mailer error. Hosts that + are listed as , which is the default, + are allowed to send mail to this host as long as the mail's + final destination is the local machine. Hosts that are + listed as are rejected for all mail + connections. Hosts that have the + option for their hostname are allowed to send mail for any + destination through this mail server. Configuring the <application>sendmail</application> - Access Database + Access Database - cyberspammer.com 550 We do not accept mail from spammers + cyberspammer.com 550 We do not accept mail from spammers FREE.STEALTH.MAILER@ 550 We do not accept mail from spammers another.source.of.spam REJECT okay.cyberspammer.com OK 128.32 RELAY - In this example we have five entries. Mail senders that - match the left hand side of the table are affected by the action - on the right side of the table. The first two examples give an - error code to sendmail's error - handling routine. The message is printed to the remote host when - a mail matches the left hand side of the table. The next entry - rejects mail from a specific host on the Internet, - another.source.of.spam. The next entry accepts - mail connections from a host - okay.cyberspammer.com, which is more exact than - the cyberspammer.com line above. More specific - matches override less exact matches. The last entry allows - relaying of electronic mail from hosts with an IP address that - begins with 128.32. These hosts would be able - to send mail through this mail server that are destined for other - mail servers. - - When this file is updated, you need to run - make in /etc/mail/ to - update the database. - - - - <filename>/etc/mail/aliases</filename> - - The aliases database contains a list of virtual mailboxes - that are expanded to other user(s), files, programs or other - aliases. Here are a few examples that can be used in - /etc/mail/aliases: + In this example we have five entries. Mail senders that + match the left hand side of the table are affected by the + action on the right side of the table. The first two examples + give an error code to sendmail's + error handling routine. The message is printed to the remote + host when a mail matches the left hand side of the table. + The next entry rejects mail from a specific host on the + Internet, another.source.of.spam. The next + entry accepts mail connections from a host okay.cyberspammer.com, which is + more exact than the cyberspammer.com line above. + More specific matches override less exact matches. The last + entry allows relaying of electronic mail from hosts with an + IP address that begins with 128.32. These + hosts would be able to send mail through this mail server + that are destined for other mail servers. + + When this file is updated, you need to run + make in /etc/mail/ + to update the database. + + + + <filename>/etc/mail/aliases</filename> + + The aliases database contains a list of virtual mailboxes + that are expanded to other user(s), files, programs or other + aliases. Here are a few examples that can be used in + /etc/mail/aliases: Mail Aliases - root: localuser + + root: localuser ftp-bugs: joe,eric,paul bit.bucket: /dev/null procmail: "|/usr/local/bin/procmail" The file format is simple; the mailbox name on the left - side of the colon is expanded to the target(s) on the right. - The - first example expands the mailbox root - to the mailbox localuser, which is then - looked up again in the aliases database. If no match is found, - then the message is delivered to the local user - localuser. The next example shows a mail - list. Mail to the mailbox ftp-bugs is - expanded to the three local mailboxes joe, - eric, and paul. Note - that a remote mailbox could be specified as user@example.com. The - next example shows writing mail to a file, in this case - /dev/null. The last example shows sending - mail to a program, in this case the mail message is written to the - standard input of /usr/local/bin/procmail - through a &unix; pipe. - - When this file is updated, you need to run - make in /etc/mail/ to - update the database. - - - <filename>/etc/mail/local-host-names</filename> + side of the colon is expanded to the target(s) on the right. + The first example expands the mailbox + root to the mailbox + localuser, which is then looked up again + in the aliases database. If no match is found, then the + message is delivered to the local user + localuser. The next example shows a + mail list. Mail to the mailbox ftp-bugs + is expanded to the three local mailboxes + joe, eric, and + paul. Note that a remote mailbox could + be specified as user@example.com. The next + example shows writing mail to a file, in this case + /dev/null. The last example shows + sending mail to a program, in this case the mail message is + written to the standard input of + /usr/local/bin/procmail through a &unix; + pipe. + + When this file is updated, you need to run + make in /etc/mail/ + to update the database. + + + <filename>/etc/mail/local-host-names</filename> - This is a list of hostnames &man.sendmail.8; is to accept as - the local host name. Place any domains or hosts that - sendmail is to be receiving mail for. - For example, if this mail server was to accept mail for the - domain example.com and the host - mail.example.com, its - local-host-names might look something like - this: + This is a list of hostnames &man.sendmail.8; is to accept + as the local host name. Place any domains or hosts that + sendmail is to be receiving mail + for. For example, if this mail server was to accept mail for + the domain example.com and + the host mail.example.com, its + local-host-names might look something + like this: - example.com + example.com mail.example.com When this file is updated, &man.sendmail.8; needs to be - restarted to read the changes. + restarted to read the changes. @@ -595,16 +615,18 @@ mail.example.com sendmail's master configuration file, sendmail.cf controls the overall - behavior of sendmail, including everything - from rewriting e-mail addresses to printing rejection messages to - remote mail servers. Naturally, with such a diverse role, this - configuration file is quite complex and its details are a bit - out of the scope of this section. Fortunately, this file rarely - needs to be changed for standard mail servers. + behavior of sendmail, including + everything from rewriting e-mail addresses to printing rejection + messages to remote mail servers. Naturally, with such a diverse + role, this configuration file is quite complex and its details + are a bit out of the scope of this section. Fortunately, this + file rarely needs to be changed for standard mail + servers. The master sendmail configuration - file can be built from &man.m4.1; macros that define the features - and behavior of sendmail. Please see + file can be built from &man.m4.1; macros that define the + features and behavior of sendmail. + Please see /usr/src/contrib/sendmail/cf/README for some of the details. @@ -616,52 +638,57 @@ mail.example.com <filename>/etc/mail/virtusertable</filename> - The virtusertable maps mail addresses for - virtual domains and - mailboxes to real mailboxes. These mailboxes can be local, - remote, aliases defined in + The virtusertable maps mail addresses + for virtual domains and mailboxes to real mailboxes. These + mailboxes can be local, remote, aliases defined in /etc/mail/aliases or files. - Example Virtual Domain Mail Map + Example Virtual Domain Mail Map - root@example.com root + root@example.com root postmaster@example.com postmaster@noc.example.net @example.com joe - In the above example, we have a mapping for a domain - example.com. This file is processed in a - first match order down the file. The first item maps - root@example.com to the local mailbox root. The next entry maps - postmaster@example.com to the mailbox postmaster on the host - noc.example.net. Finally, if nothing from example.com has - matched so far, it will match the last mapping, which matches - every other mail message addressed to someone at - example.com. - This will be mapped to the local mailbox joe. + In the above example, we have a mapping for a domain + example.com. This file + is processed in a first match order down the file. The first + item maps root@example.com to the local mailbox + root. The next entry maps + postmaster@example.com to the mailbox + postmaster on the host + noc.example.net. Finally, if + nothing from example.com + has matched so far, it will match the last mapping, which + matches every other mail message addressed to someone at + example.com. This will + be mapped to the local mailbox + joe. - + - - Andrew - Boothman - Written by - + + Andrew + Boothman + Written by + - - Gregory - Neil Shapiro - Information taken from e-mails written by - + + Gregory + Neil Shapiro + Information taken from e-mails written + by + Changing Your Mail Transfer Agent + email change mta @@ -694,8 +721,8 @@ postmaster@example.com postmast needs, and also gives you the opportunity to configure your new software before getting it to take over from sendmail. When doing this, you - should be sure that installing the new software will not attempt - to overwrite system binaries such as + should be sure that installing the new software will not + attempt to overwrite system binaries such as /usr/bin/sendmail. Otherwise, your new mail software has essentially been put into service before you have configured it. @@ -708,32 +735,32 @@ postmaster@example.com postmast Disable <application>sendmail</application> - - If you disable sendmail's - outgoing mail service, it is important that you replace it - with an alternative mail delivery system. If - you choose not to, system functions such as &man.periodic.8; - will be unable to deliver their results by e-mail as they - would normally expect to. Many parts of your system may - expect to have a functional - sendmail-compatible system. If - applications continue to use - sendmail's binaries to try to send - e-mail after you have disabled them, mail could go into an - inactive sendmail queue, and - never be delivered. - + + If you disable sendmail's + outgoing mail service, it is important that you replace it + with an alternative mail delivery system. If + you choose not to, system functions such as + &man.periodic.8; will be unable to deliver their results + by e-mail as they would normally expect to. Many parts of + your system may expect to have a functional + sendmail-compatible system. If + applications continue to use + sendmail's binaries to try to + send e-mail after you have disabled them, mail could go + into an inactive sendmail queue, + and never be delivered. + - In order to completely disable - sendmail, including the outgoing - mail service, you must use + In order to completely disable + sendmail, including the outgoing + mail service, you must use - sendmail_enable="NO" + sendmail_enable="NO" sendmail_submit_enable="NO" sendmail_outbound_enable="NO" sendmail_msp_queue_enable="NO" - in /etc/rc.conf. + in /etc/rc.conf. If you only want to disable sendmail's incoming mail service, @@ -741,19 +768,22 @@ sendmail_msp_queue_enable="NO"sendmail_enable="NO" - in /etc/rc.conf. More information on - sendmail's startup options is - available from the &man.rc.sendmail.8; manual page. - - - - Running Your New MTA on Boot + in /etc/rc.conf. More information + on sendmail's startup options + is available from the &man.rc.sendmail.8; manual + page. + - The new MTA can be started during boot by adding a - configuration line to /etc/rc.conf - like the following example for postfix: + + Running Your New MTA on Boot - &prompt.root; echo 'postfix_enable=YES' >> /etc/rc.conf + The new MTA can be started during boot by adding a + configuration line to /etc/rc.conf + like the following example for postfix: + + &prompt.root; echo +'postfix_enable=YES' +>> /etc/rc.conf The MTA will now be automatically started during boot. @@ -761,15 +791,16 @@ sendmail_msp_queue_enable="NO" Replacing <application>sendmail</application> as - the System's Default Mailer + the System's Default Mailer - The program sendmail is so ubiquitous - as standard software on &unix; systems that some software - just assumes it is already installed and configured. - For this reason, many alternative MTA's provide their own compatible - implementations of the sendmail - command-line interface; this facilitates using them as - drop-in replacements for sendmail. + The program sendmail is so + ubiquitous as standard software on &unix; systems that some + software just assumes it is already installed and configured. + For this reason, many alternative MTA's provide their own + compatible implementations of the + sendmail command-line interface; + this facilitates using them as drop-in + replacements for sendmail. Therefore, if you are using an alternative mailer, you will need to make sure that software trying to execute @@ -779,11 +810,11 @@ sendmail_msp_queue_enable="NO" *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-all@FreeBSD.ORG Tue Feb 12 15:09:50 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A3DBAD2; Tue, 12 Feb 2013 15:09:50 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 951F1A1D; Tue, 12 Feb 2013 15:09:50 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1CF9owj073234; Tue, 12 Feb 2013 15:09:50 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1CF9ojQ073233; Tue, 12 Feb 2013 15:09:50 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201302121509.r1CF9ojQ073233@svn.freebsd.org> From: Dru Lavigne Date: Tue, 12 Feb 2013 15:09:50 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40958 - head/en_US.ISO8859-1/books/handbook/introduction X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Feb 2013 15:09:50 -0000 Author: dru Date: Tue Feb 12 15:09:50 2013 New Revision: 40958 URL: http://svnweb.freebsd.org/changeset/doc/40958 Log: White space fix only. Translators can ignore. Approved by: gjb (mentor) Modified: head/en_US.ISO8859-1/books/handbook/introduction/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/introduction/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/introduction/chapter.xml Tue Feb 12 14:40:47 2013 (r40957) +++ head/en_US.ISO8859-1/books/handbook/introduction/chapter.xml Tue Feb 12 15:09:50 2013 (r40958) @@ -23,14 +23,15 @@ Synopsis Thank you for your interest in &os;! The following chapter - covers various aspects of the &os; Project, such as its history, - goals, development model, and so on. + covers various aspects of the &os; Project, such as its + history, goals, development model, and so on. After reading this chapter, you will know: - How &os; relates to other computer operating systems. + How &os; relates to other computer operating + systems. @@ -42,7 +43,8 @@ - The basics of the &os; open-source development model. + The basics of the &os; open-source development + model. @@ -65,7 +67,8 @@ or the current release. If you are interested in contributing something to the Project (code, hardware, funding), see the Contributing to &os; article. + url="&url.articles.contributing;/index.html">Contributing to + &os; article. What Can &os; Do? @@ -75,51 +78,55 @@ - preemptive multitasking + preemptive + multitasking Preemptive multitasking with dynamic priority adjustment to ensure smooth and fair - sharing of the computer between applications and users, even - under the heaviest of loads. + sharing of the computer between applications and users, + even under the heaviest of loads. - multi-user facilities + multi-user + facilities - Multi-user facilities which allow many - people to use a &os; system simultaneously for a variety - of things. This means, for example, that system peripherals - such as printers and tape drives are properly shared between - all users on the system or the network and that individual - resource limits can be placed on users or groups of users, - protecting critical system resources from over-use. + Multi-user facilities which allow + many people to use a &os; system simultaneously for a + variety of things. This means, for example, that system + peripherals such as printers and tape drives are properly + shared between all users on the system or the network and + that individual resource limits can be placed on users or + groups of users, protecting critical system resources from + over-use. TCP/IP networking Strong TCP/IP networking with support for industry standards such as SCTP, DHCP, NFS, - NIS, PPP, SLIP, IPsec, and IPv6. This means that your &os; - machine can interoperate easily with other systems as well as - act as an enterprise server, providing vital functions such as NFS - (remote file access) and email services or putting your - organization on the Internet with WWW, FTP, routing and - firewall (security) services. + NIS, PPP, SLIP, IPsec, and IPv6. This means that your + &os; machine can interoperate easily with other systems as + well as act as an enterprise server, providing vital + functions such as NFS (remote file access) and email + services or putting your organization on the Internet with + WWW, FTP, routing and firewall (security) services. memory protection Memory protection ensures that - applications (or users) cannot interfere with each other. One - application crashing will not affect others in any way. + applications (or users) cannot interfere with each other. + One application crashing will not affect others in any + way. &os; is a 32-bit operating system (64-bit on the &itanium;, - AMD64, and &ultrasparc;) and was designed as such from the ground - up. + AMD64, and &ultrasparc;) and was designed as such from + the ground up. @@ -127,60 +134,63 @@ X Window System - The industry standard X Window System - (X11R7) provides a graphical user interface (GUI) for the cost - of a common VGA card and monitor and comes with full - sources. + The industry standard X Window + System (X11R7) provides a graphical user + interface (GUI) for the cost of a common VGA card and + monitor and comes with full sources. - - binary compatibility - Linux - - - binary compatibility - SCO - - - binary compatibility - SVR4 - - - binary compatibility - BSD/OS - - - binary compatibility - NetBSD - + + binary compatibility + Linux + + + binary compatibility + SCO + + + binary compatibility + SVR4 + + + binary compatibility + BSD/OS + + + binary compatibility + NetBSD + Binary compatibility with many - programs built for Linux, SCO, SVR4, BSDI and NetBSD. + programs built for Linux, SCO, SVR4, BSDI and + NetBSD. Thousands of ready-to-run applications are available from the &os; - ports and packages - collection. Why search the net when you can find it all right - here? + ports and + packages collection. Why search the + net when you can find it all right here? Thousands of additional and - easy-to-port applications are available - on the Internet. &os; is source code compatible with most - popular commercial &unix; systems and thus most applications - require few, if any, changes to compile. + easy-to-port applications are + available on the Internet. &os; is source code compatible + with most popular commercial &unix; systems and thus most + applications require few, if any, changes to + compile. virtual memory Demand paged virtual memory and merged VM/buffer cache design efficiently - satisfies applications with large appetites for memory while - still maintaining interactive response to other users. + satisfies applications with large appetites for memory + while still maintaining interactive response to other + users. @@ -206,8 +216,8 @@ and C++ development tools. Many additional languages for advanced research - and development are also available in the ports and packages - collection. + and development are also available in the ports and + packages collection. @@ -222,7 +232,7 @@ Extensive online - documentation. + documentation. @@ -236,39 +246,42 @@ U.C. Berkeley &os; is based on the 4.4BSD-Lite release from Computer - Systems Research Group (CSRG) at the University of California at - Berkeley, and carries on the distinguished tradition of BSD + Systems Research Group (CSRG) at the University of California + at Berkeley, and carries on the distinguished tradition of BSD systems development. In addition to the fine work provided by - CSRG, the &os; Project has put in many thousands of hours in - fine tuning the system for maximum performance and reliability in - real-life load situations. As many of the commercial giants - struggle to field PC operating systems with such features, - performance and reliability, &os; can offer them - now! + CSRG, the &os; Project has put in many thousands of hours + in fine tuning the system for maximum performance and + reliability in real-life load situations. As many of the + commercial giants struggle to field PC operating systems with + such features, performance and reliability, &os; can offer + them now! The applications to which &os; can be put are truly - limited only by your own imagination. From software development - to factory automation, inventory control to azimuth correction of - remote satellite antennae; if it can be done with a commercial - &unix; product then it is more than likely that you can do it with - &os; too! &os; also benefits significantly from - literally thousands of high quality applications developed by - research centers and universities around the world, often - available at little to no cost. Commercial applications are also - available and appearing in greater numbers every day. + limited only by your own imagination. From software + development to factory automation, inventory control to + azimuth correction of remote satellite antennae; if it can be + done with a commercial &unix; product then it is more than + likely that you can do it with &os; too! &os; also benefits + significantly from literally thousands of high quality + applications developed by research centers and universities + around the world, often available at little to no cost. + Commercial applications are also available and appearing in + greater numbers every day. Because the source code for &os; itself is generally - available, the system can also be customized to an almost unheard - of degree for special applications or projects, and in ways not - generally possible with operating systems from most major - commercial vendors. Here is just a sampling of some of the - applications in which people are currently using &os;: + available, the system can also be customized to an almost + unheard of degree for special applications or projects, and in + ways not generally possible with operating systems from most + major commercial vendors. Here is just a sampling of some of + the applications in which people are currently using + &os;: - Internet Services: The robust TCP/IP - networking built into &os; makes it an ideal platform for a - variety of Internet services such as: + Internet Services: The robust + TCP/IP networking built into &os; makes it an ideal + platform for a variety of Internet services such + as: @@ -298,13 +311,13 @@ - - electronic mail - email - - - email - + + electronic mail + email + + + email + Electronic Mail servers @@ -328,25 +341,25 @@ Education: Are you a student of - computer science or a related engineering field? There is no - better way of learning about operating systems, computer - architecture and networking than the hands on, under the hood - experience that &os; can provide. A number of freely - available CAD, mathematical and graphic design packages also - make it highly useful to those whose primary interest in a - computer is to get other work - done! + computer science or a related engineering field? There + is no better way of learning about operating systems, + computer architecture and networking than the hands on, + under the hood experience that &os; can provide. A number + of freely available CAD, mathematical and graphic design + packages also make it highly useful to those whose primary + interest in a computer is to get + other work done! - Research: With source code for the - entire system available, &os; is an excellent platform for - research in operating systems as well as other branches of - computer science. &os;'s freely available nature also makes - it possible for remote groups to collaborate on ideas or - shared development without having to worry about special - licensing agreements or limitations on what may be discussed - in open forums. + Research: With source code for + the entire system available, &os; is an excellent platform + for research in operating systems as well as other + branches of computer science. &os;'s freely available + nature also makes it possible for remote groups to + collaborate on ideas or shared development without having + to worry about special licensing agreements or limitations + on what may be discussed in open forums. @@ -354,34 +367,35 @@ DNS Server - Networking: Need a new router? A - name server (DNS)? A firewall to keep people out of your + Networking: Need a new router? + A name server (DNS)? A firewall to keep people out of your internal network? &os; can easily turn that unused 386 or 486 PC sitting in the corner into an advanced router with sophisticated packet-filtering capabilities. - - X Window System - - - X Window System - Accelerated-X - + + X Window System + + + X Window System + Accelerated-X + X Window workstation: &os; is a fine choice for an inexpensive X terminal solution, using the freely available X11 server. - Unlike an X terminal, &os; allows many applications to be run - locally if desired, thus relieving the burden on a central - server. &os; can even boot diskless, making - individual workstations even cheaper and easier to - administer. + Unlike an X terminal, &os; allows many applications to + be run locally if desired, thus relieving the burden on a + central server. &os; can even boot + diskless, making individual workstations + even cheaper and easier to administer. - GNU Compiler Collection + GNU Compiler + Collection Software Development: The basic &os; system comes with a full complement of development @@ -390,9 +404,10 @@ - &os; is available in both source and binary form on CD-ROM, - DVD, and via anonymous FTP. Please see - for more information about obtaining &os;. + &os; is available in both source and binary form on + CD-ROM, DVD, and via anonymous FTP. Please see for more information about obtaining + &os;. @@ -404,51 +419,59 @@ &os; is used as a platform for devices and products from - many of the world's largest IT companies, including: + many of the world's largest IT companies, including: Apple - Apple + Apple Cisco - Cisco + Cisco - Juniper + Juniper NetApp - NetApp + NetApp - &os; is also used to power some of the biggest sites on the - Internet, including: + &os; is also used to power some of the biggest sites on + the Internet, including: Yahoo! - Yahoo! + Yahoo! Yandex - Yandex + Yandex Apache - Apache + Apache Rambler - Rambler + Rambler @@ -459,45 +482,50 @@ Pair Networks - Pair Networks + Pair Networks Sony Japan - Sony Japan + Sony Japan Netcraft - Netcraft + Netcraft NetEase - NetEase + NetEase Weathernews - Weathernews + Weathernews TELEHOUSE America TELEHOUSE - America + America Experts Exchange Experts - Exchange + Exchange @@ -508,9 +536,9 @@ About the &os; Project - The following section provides some background information on - the project, including a brief history, project goals, and the - development model of the project. + The following section provides some background information + on the project, including a brief history, project goals, and + the development model of the project. @@ -533,109 +561,116 @@ FreeBSD Project history - The &os; Project had its genesis in the early part of 1993, - partially as an outgrowth of the Unofficial 386BSD - Patchkit by the patchkit's last 3 coordinators: Nate - Williams, Rod Grimes and myself. + The &os; Project had its genesis in the early part + of 1993, partially as an outgrowth of the Unofficial + 386BSDPatchkit by the patchkit's last 3 + coordinators: Nate Williams, Rod Grimes and myself. 386BSD - Our original goal was to produce an intermediate snapshot of - 386BSD in order to fix a number of problems with it that the - patchkit mechanism just was not capable of solving. Some of you - may remember the early working title for the project being - 386BSD 0.5 or 386BSD Interim in - reference to that fact. + Our original goal was to produce an intermediate snapshot + of 386BSD in order to fix a number of problems with it that + the patchkit mechanism just was not capable of solving. Some + of you may remember the early working title for the project + being 386BSD 0.5 or 386BSD + Interim in reference to that fact. Jolitz, Bill - 386BSD was Bill Jolitz's operating system, which had been up - to that point suffering rather severely from almost a year's worth - of neglect. As the patchkit swelled ever more uncomfortably with - each passing day, we were in unanimous agreement that something - had to be done and decided to assist Bill by providing - this interim cleanup snapshot. Those plans came to - a rude halt when Bill Jolitz suddenly decided to withdraw his - sanction from the project without any clear indication of what - would be done instead. + 386BSD was Bill Jolitz's operating system, which had been + up to that point suffering rather severely from almost a + year's worth of neglect. As the patchkit swelled ever more + uncomfortably with each passing day, we were in unanimous + agreement that something had to be done and decided to assist + Bill by providing this interim cleanup + snapshot. Those plans came to a rude halt when Bill Jolitz + suddenly decided to withdraw his sanction from the project + without any clear indication of what would be done + instead. Greenman, David Walnut Creek CDROM It did not take us long to decide that the goal remained worthwhile, even without Bill's support, and so we adopted the - name &os;, coined by David Greenman. Our initial - objectives were set after consulting with the system's current - users and, once it became clear that the project was on the road - to perhaps even becoming a reality, I contacted Walnut Creek CDROM - with an eye toward improving &os;'s distribution channels for - those many unfortunates without easy access to the Internet. - Walnut Creek CDROM not only supported the idea of distributing - &os; on CD but also went so far as to provide the project with a - machine to work on and a fast Internet connection. Without Walnut - Creek CDROM's almost unprecedented degree of faith in what was, at - the time, a completely unknown project, it is quite unlikely that - &os; would have gotten as far, as fast, as it has today. + name &os;, coined by David Greenman. Our + initial objectives were set after consulting with the system's + current users and, once it became clear that the project was + on the road to perhaps even becoming a reality, I contacted + Walnut Creek CDROM with an eye toward improving &os;'s + distribution channels for those many unfortunates without easy + access to the Internet. Walnut Creek CDROM not only supported + the idea of distributing &os; on CD but also went so far as to + provide the project with a machine to work on and a fast + Internet connection. Without Walnut Creek CDROM's almost + unprecedented degree of faith in what was, at the time, a + completely unknown project, it is quite unlikely that &os; + would have gotten as far, as fast, as it has today. 4.3BSD-Lite Net/2 U.C. Berkeley 386BSD - Free Software Foundation + Free Software + Foundation The first CD-ROM (and general net-wide) distribution was - &os; 1.0, released in December of 1993. This was based on the - 4.3BSD-Lite (Net/2) tape from U.C. Berkeley, with - many components also provided by 386BSD and the Free Software - Foundation. It was a fairly reasonable success for a first - offering, and we followed it with the highly successful &os; - 1.1 release in May of 1994. + &os; 1.0, released in December of 1993. This was based + on the 4.3BSD-Lite (Net/2) tape from U.C. + Berkeley, with many components also provided by 386BSD and the + Free Software Foundation. It was a fairly reasonable success + for a first offering, and we followed it with the highly + successful &os; 1.1 release in May of 1994. Novell U.C. Berkeley Net/2 AT&T - Around this time, some rather unexpected storm clouds formed - on the horizon as Novell and U.C. Berkeley settled their - long-running lawsuit over the legal status of the Berkeley Net/2 - tape. A condition of that settlement was U.C. Berkeley's - concession that large parts of Net/2 were encumbered - code and the property of Novell, who had in turn acquired it from - AT&T some time previously. What Berkeley got in return was - Novell's blessing that the 4.4BSD-Lite release, when - it was finally released, would be declared unencumbered and all - existing Net/2 users would be strongly encouraged to switch. This - included &os;, and the project was given until the end of July - 1994 to stop shipping its own Net/2 based product. Under the - terms of that agreement, the project was allowed one last release - before the deadline, that release being &os; 1.1.5.1. + Around this time, some rather unexpected storm clouds + formed on the horizon as Novell and U.C. Berkeley settled + their long-running lawsuit over the legal status of the + Berkeley Net/2 tape. A condition of that settlement was U.C. + Berkeley's concession that large parts of Net/2 were + encumbered code and the property of Novell, who + had in turn acquired it from AT&T some time previously. + What Berkeley got in return was Novell's + blessing that the 4.4BSD-Lite release, when + it was finally released, would be declared unencumbered and + all existing Net/2 users would be strongly encouraged to + switch. This included &os;, and the project was given until + the end of July 1994 to stop shipping its own Net/2 based + product. Under the terms of that agreement, the project was + allowed one last release before the deadline, that release + being &os; 1.1.5.1. &os; then set about the arduous task of literally - re-inventing itself from a completely new and rather incomplete - set of 4.4BSD-Lite bits. The Lite releases were - light in part because Berkeley's CSRG had removed large chunks of - code required for actually constructing a bootable running system - (due to various legal requirements) and the fact that the Intel - port of 4.4 was highly incomplete. It took the project until - November of 1994 to make this transition, at which point it - released &os; 2.0 to the net and on CD-ROM (in late December). + re-inventing itself from a completely new and rather + incomplete set of 4.4BSD-Lite bits. The Lite + releases were light in part because Berkeley's CSRG had + removed large chunks of code required for actually + constructing a bootable running system (due to various legal + requirements) and the fact that the Intel port of 4.4 was + highly incomplete. It took the project until November of 1994 + to make this transition, at which point it released + &os; 2.0 to the net and on CD-ROM (in late December). Despite being still more than a little rough around the edges, the release was a significant success and was followed by the - more robust and easier to install &os; 2.0.5 release in June of - 1995. + more robust and easier to install &os; 2.0.5 release in + June of 1995. - We released &os; 2.1.5 in August of 1996, and it appeared - to be popular enough among the ISP and commercial communities that - another release along the 2.1-STABLE branch was merited. This was - &os; 2.1.7.1, released in February 1997 and capping the end of - mainstream development on 2.1-STABLE. Now in maintenance mode, - only security enhancements and other critical bug fixes will be - done on this branch (RELENG_2_1_0). + We released &os; 2.1.5 in August of 1996, and it + appeared to be popular enough among the ISP and commercial + communities that another release along the 2.1-STABLE branch + was merited. This was &os; 2.1.7.1, released in February + 1997 and capping the end of mainstream development on + 2.1-STABLE. Now in maintenance mode, only security + enhancements and other critical bug fixes will be done on this + branch (RELENG_2_1_0). &os; 2.2 was branched from the development mainline (-CURRENT) in November 1996 as the RELENG_2_2 - branch, and the first full release (2.2.1) was released in April - 1997. Further releases along the 2.2 branch were done in the - summer and fall of '97, the last of which (2.2.8) appeared in - November 1998. The first official 3.0 release appeared in - October 1998 and spelled the beginning of the end for the 2.2 - branch. + branch, and the first full release (2.2.1) was released in + April 1997. Further releases along the 2.2 branch were done + in the summer and fall of '97, the last of which (2.2.8) + appeared in November 1998. The first official 3.0 release + appeared in October 1998 and spelled the beginning of the end + for the 2.2 branch. The tree branched again on Jan 20, 1999, leading to the 4.0-CURRENT and 3.X-STABLE branches. From 3.X-STABLE, 3.1 was @@ -643,58 +678,61 @@ September 16, 1999, 3.4 on December 20, 1999, and 3.5 on June 24, 2000, which was followed a few days later by a minor point release update to 3.5.1, to incorporate some last-minute - security fixes to Kerberos. This will be the final release in the - 3.X branch. + security fixes to Kerberos. This will be the final release + in the 3.X branch. There was another branch on March 13, 2000, which saw the - emergence of the 4.X-STABLE branch. There have been several releases - from it so far: 4.0-RELEASE was introduced in March 2000, and - the last 4.11-RELEASE came out in January 2005. + emergence of the 4.X-STABLE branch. There have been several + releases from it so far: 4.0-RELEASE was introduced in March + 2000, and the last 4.11-RELEASE came out in January + 2005. The long-awaited 5.0-RELEASE was announced on January 19, 2003. The culmination of nearly three years of work, this release started &os; on the path of advanced multiprocessor and application thread support and introduced support for the - &ultrasparc; and ia64 platforms. This release - was followed by 5.1 in June of 2003. The last 5.X release from the - -CURRENT branch was 5.2.1-RELEASE, introduced in February 2004. - - The RELENG_5 branch, created in August 2004, was followed by - 5.3-RELEASE, which marked the beginning of the 5-STABLE branch - releases. The most recent 5.5-RELEASE release came out in May 2006. - There will be no additional releases from the RELENG_5 branch. - - The tree was branched again in July 2005, this time for RELENG_6. - 6.0-RELEASE, the first release of the 6.X branch, was released in - November 2005. The most recent 6.4-RELEASE came out in - November 2008. There will be no additional releases from the - RELENG_6 branch. This branch is the last branch to support the - Alpha architecture. + &ultrasparc; and ia64 platforms. This + release was followed by 5.1 in June of 2003. The last 5.X + release from the -CURRENT branch was 5.2.1-RELEASE, introduced + in February 2004. + + The RELENG_5 branch, created in August 2004, was followed + by 5.3-RELEASE, which marked the beginning of the 5-STABLE + branch releases. The most recent 5.5-RELEASE release came out + in May 2006. There will be no additional releases from the + RELENG_5 branch. + + The tree was branched again in July 2005, this time for + RELENG_6. 6.0-RELEASE, the first release of the 6.X branch, + was released in November 2005. The most recent 6.4-RELEASE + came out in November 2008. There will be no additional + releases from the RELENG_6 branch. This branch is the last + branch to support the Alpha architecture. - The RELENG_7 branch was created in October 2007. The first - release of this branch was 7.0-RELEASE, which came + The RELENG_7 branch was created in October 2007. The + first release of this branch was 7.0-RELEASE, which came out in February 2008. The most recent 7.4-RELEASE came out - in February 2011. There will be no additional releases from the - RELENG_7 branch. + in February 2011. There will be no additional releases from + the RELENG_7 branch. The tree was branched again in August 2009, this time for - RELENG_8. 8.0-RELEASE, the first release of the 8.X branch, was - released in November 2009. The most recent - &rel2.current;-RELEASE came out in &rel2.current.date;. There will - be additional releases from the RELENG_8 branch. - - The RELENG_9 branch was created in September 2011. The first - release of this branch was 9.0-RELEASE, which came - out in January 2012. The most recent &rel.current;-RELEASE came - out in &rel.current.date;. There will be additional releases - from the RELENG_9 branch. - - For now, long-term development projects continue to take place - in the 10.X-CURRENT (trunk) branch, and SNAPshot releases of 10.X on - CD-ROM (and, of course, on the net) are continually made available - from the snapshot - server as work progresses. + RELENG_8. 8.0-RELEASE, the first release of the 8.X branch, + was released in November 2009. The most recent + &rel2.current;-RELEASE came out in &rel2.current.date;. There + will be additional releases from the RELENG_8 branch. + + The RELENG_9 branch was created in September 2011. The + first release of this branch was 9.0-RELEASE, which came + out in January 2012. The most recent &rel.current;-RELEASE + came out in &rel.current.date;. There will be additional + releases from the RELENG_9 branch. + + For now, long-term development projects continue to take + place in the 10.X-CURRENT (trunk) branch, and SNAPshot + releases of 10.X on CD-ROM (and, of course, on the net) are + continually made available from the + snapshot server as work progresses. @@ -714,17 +752,17 @@ FreeBSD Project goals - The goals of the &os; Project are to provide software that - may be used for any purpose and without strings attached. Many of - us have a significant investment in the code (and project) and - would certainly not mind a little financial compensation now and - then, but we are definitely not prepared to insist on it. We - believe that our first and foremost mission is to - provide code to any and all comers, and for whatever purpose, so - that the code gets the widest possible use and provides the widest - possible benefit. This is, I believe, one of the most fundamental - goals of Free Software and one that we enthusiastically - support. + The goals of the &os; Project are to provide software + that may be used for any purpose and without strings attached. + Many of us have a significant investment in the code (and + project) and would certainly not mind a little financial + compensation now and then, but we are definitely not prepared + to insist on it. We believe that our first and foremost + mission is to provide code to any and all + comers, and for whatever purpose, so that the code gets the + widest possible use and provides the widest possible benefit. + This is, I believe, one of the most fundamental goals of Free + Software and one that we enthusiastically support. GNU General Public License (GPL) @@ -765,14 +803,14 @@ of hundreds of people around the world, as can be seen from our list of - contributors. &os;'s development infrastructure allow - these hundreds of developers to collaborate over the Internet. - We are constantly on the lookout for - new developers and ideas, and those interested in becoming - more closely involved with the project need simply contact us - at the &a.hackers;. The &a.announce; is also available to - those wishing to make other &os; users aware of major areas - of work. + contributors. &os;'s development infrastructure + allow these hundreds of developers to collaborate over the + Internet. We are constantly on the lookout for new developers + and ideas, and those interested in becoming more closely + involved with the project need simply contact us at the + &a.hackers;. The &a.announce; is also available to those + wishing to make other &os; users aware of major areas of + work. Useful things to know about the &os; Project and its development process, whether working independently or in close @@ -812,16 +850,17 @@ For several years, the central source tree for &os; was maintained by CVS - (Concurrent Versions System), a freely available source code - control tool that comes bundled with &os;. In June 2008, the - Project switched to using SVN (Subversion). - The switch was deemed necessary, as the technical limitations - imposed by CVS were becoming obvious - due to the rapid expansion of the source tree and the amount - of history already stored. The Documentation Project - and Ports Collection repositories also moved from - CVS to + (Concurrent Versions System), a freely available source + code control tool that comes bundled with &os;. In June + 2008, the Project switched to using SVN + (Subversion). The switch was deemed necessary, as the + technical limitations imposed by + CVS were becoming obvious + due to the rapid expansion of the source tree and the + amount of history already stored. The Documentation + Project and Ports Collection repositories also moved + from CVS to SVN in May 2012 and July 2012, respectively. @@ -829,10 +868,10 @@ ports/ repositories now use SVN, client side tools like csup that depend on the older - CVS infrastructure, continue to - work normally — changes in the - SVN repository are backported to - CVS for this purpose. + CVS infrastructure, continue + to work normally — changes in the + SVN repository are backported + to CVS for this purpose. Unlike src/ and ports/, the documentation SVN @@ -844,11 +883,12 @@ url="http://www.FreeBSD.org/cgi/cvsweb.cgi">repository resides on a machine in Santa Clara CA, USA from where it is replicated to numerous mirror machines - throughout the world. The SVN tree, - which contains the -CURRENT and - -STABLE trees, - can all be easily replicated to your own machine as well. - Please refer to the Synchronizing + throughout the world. The + SVN tree, which contains the + -CURRENT and -STABLE trees, can all be + easily replicated to your own machine as well. Please + refer to the Synchronizing your source tree section for more information on doing this. @@ -862,36 +902,37 @@ committers The committers - are the people who have write access to - the Subversion tree, and are authorized to make modifications - to the &os; source (the term committer - comes from the source control commit - command, which is used to bring new changes into the - repository). The best way of making submissions for review - by the committers list is to use the &man.send-pr.1; - command. If something appears to be jammed in the - system, then you may also reach them by sending mail to - the &a.committers;. + are the people who have write + access to the Subversion tree, and are authorized to + make modifications to the &os; source (the term + committer comes from the source control *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-all@FreeBSD.ORG Tue Feb 12 15:13:12 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id EDAF61BD; Tue, 12 Feb 2013 15:13:12 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id DF0DCA3E; Tue, 12 Feb 2013 15:13:12 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1CFDCXu075490; Tue, 12 Feb 2013 15:13:12 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1CFDCBh075489; Tue, 12 Feb 2013 15:13:12 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201302121513.r1CFDCBh075489@svn.freebsd.org> From: Dru Lavigne Date: Tue, 12 Feb 2013 15:13:12 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40959 - head/en_US.ISO8859-1/books/handbook/config X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Feb 2013 15:13:13 -0000 Author: dru Date: Tue Feb 12 15:13:12 2013 New Revision: 40959 URL: http://svnweb.freebsd.org/changeset/doc/40959 Log: This first patch addresses the following: - rewording to remove you/we/please/simply/etc./i.e./as well as - one &os; replacement - reword sections that mention ISA - some rewording for redundancy; some areas weren't touched as they need to be completely rewritten - some ACPI/APM fixups Approved by: gjb (mentor) Modified: head/en_US.ISO8859-1/books/handbook/config/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/config/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/config/chapter.xml Tue Feb 12 15:09:50 2013 (r40958) +++ head/en_US.ISO8859-1/books/handbook/config/chapter.xml Tue Feb 12 15:13:12 2013 (r40959) @@ -38,25 +38,24 @@ system configuration system optimization - One of the important aspects of &os; is system - configuration. Correct system configuration will help prevent - headaches during future upgrades. This chapter will explain - much of the &os; configuration process, including some of the - parameters which can be set to tune a &os; system. + One of the important aspects of &os; is proper system + configuration. This chapter explains much of the &os; + configuration process, including some of the parameters which + can be set to tune a &os; system. After reading this chapter, you will know: - How to efficiently work with - file systems and swap partitions. + How to efficiently work with file systems and swap + partitions. The basics of rc.conf configuration and /usr/local/etc/rc.d startup - systems. + scripts. @@ -64,7 +63,7 @@ - How to configure virtual hosts on your network + How to configure virtual hosts on network devices. @@ -93,9 +92,8 @@ - Be familiar with the basics of kernel - configuration/compilation - (). + Be familiar with the basics of kernel configuration and + compilation (). @@ -133,13 +131,12 @@ The size of the /var partition - reflects the intended machine usage. The - /var file system is - used to hold mailboxes, log files, and printer spools. - Mailboxes and log files can grow to unexpected sizes - depending on how many users exist and how long log files are - kept. Most users will rarely need more than about a - gigabyte of free disk space in + reflects the intended machine's usage. This partition + /var is used to hold + mailboxes, log files, and printer spools. Mailboxes and log + files can grow to unexpected sizes depending on how many + users exist and how long log files are kept. Most users + rarely need more than about a gigabyte of free disk space in /var. @@ -158,11 +155,10 @@ The /usr - partition holds many of the files required to support the - system, including the &man.ports.7; collection (recommended) - and the source code (optional). Both the ports and the - sources of the base system are optional at install time, but - we recommend at least 2 gigabytes for this partition. + partition holds many of the files which support the system, + including the &os; Ports Collection and system source code. + At least 2 gigabytes is recommended for this + partition. When selecting partition sizes, keep the space requirements in mind. Running out of space in @@ -186,20 +182,17 @@ swap partition As a rule of thumb, the swap partition should be about - double the size of system memory (RAM). For example, if the - machine has 128 megabytes of memory, the swap file - should be 256 megabytes. Systems with less memory may - perform better with more swap. Less than 256 megabytes - of swap is not recommended and memory expansion should be - considered. The kernel's VM paging algorithms are tuned to - perform best when the swap partition is at least two times - the size of main memory. Configuring too little swap can - lead to inefficiencies in the VM page scanning code and + double the size of physical memory (RAM) as the kernel's + virtual memory (VM) paging algorithms are tuned to perform + best when the swap partition is at least two times + the size of main memory. Systems with minimal RAM may + perform better with more swap. Configuring too little swap + can lead to inefficiencies in the VM page scanning code and might create issues later if more memory is added. - On larger systems with multiple SCSI disks (or multiple - IDE disks operating on different controllers), it is - recommend that a swap is configured on each drive (up to + On larger systems with multiple SCSI disks or multiple + IDE disks operating on different controllers, it is + recommended that swap be configured on each drive (up to four drives). The swap partitions should be approximately the same size. The kernel can handle arbitrary sizes but internal data structures scale to 4 times the largest swap @@ -219,8 +212,8 @@ characteristics and separating them allows the file system to tune accordingly. For example, the root and /usr partitions are - read-mostly, without much writing. While a lot of reading - and writing could occur in + read-mostly, with few writes, while a lot of reads and + writes could occur in /var and /var/tmp. @@ -250,20 +243,18 @@ The principal location for system configuration information - is within /etc/rc.conf. This file contains - a wide range of configuration information, principally used at - system startup to configure the system. Its name directly - implies this; it is configuration information for the - rc* files. - - An administrator should make entries in - rc.conf to override the default - settings from /etc/defaults/rc.conf. The - defaults file should not be copied verbatim to - /etc - it contains - default values, not examples. All system-specific changes - should be made in the rc.conf file - itself. + is /etc/rc.conf. This file contains + a wide range of configuration information and it is read at + system startup to configure the system. It provides the + configuration information for the rc* + files. + + The entries in /etc/rc.conf override + the default settings in + /etc/defaults/rc.conf. The file containing + the default settings should not be edited. Instead, all + system-specific changes should be made to + /etc/rc.conf. A number of strategies may be applied in clustered applications to separate site-wide configuration from @@ -306,7 +297,7 @@ ifconfig_fxp0="inet 10.1.1.1/8"The /etc/rc.conf configuration file is parsed by &man.sh.1;. This allows system operators to add a certain amount of logic to this file, which may help to - create very complex configuration scenarios. Please see + create very complex configuration scenarios. Refer to &man.rc.conf.5; for further information on this topic. @@ -315,10 +306,10 @@ ifconfig_fxp0="inet 10.1.1.1/8"Application Configuration Typically, installed applications have their own - configuration files, with their own syntax, etc. It is - important that these files be kept separate from the base - system, so that they may be easily located and managed by the - package management tools. + configuration files and syntax. It is important that these + files be kept separate from the base system, so that they may be + easily located and managed by the package management + tools. /usr/local/etc @@ -370,10 +361,9 @@ ifconfig_fxp0="inet 10.1.1.1/8"services - Many users choose to install third party software on &os; - from the Ports Collection. In many of these situations it may - be necessary to configure the software in a manner which will - allow it to be started upon system initialization. Services, + Many users install third party software on &os; from the + Ports Collection and require the installed services to be + started upon system initialization. Services, such as mail/postfix or www/apache22 are just two of the many software packages which may be started during system @@ -381,24 +371,20 @@ ifconfig_fxp0="inet 10.1.1.1/8" In &os;, most included services, such as &man.cron.8;, are - started through the system start up scripts. These scripts may - differ depending on &os; or vendor version; however, the most - important aspect to consider is that their start up - configuration can be handled through simple startup - scripts. + started through the system start up scripts. Extended Application Configuration Now that &os; includes rc.d, - configuration of application startup has become easier, and - more featureful. Using the key words discussed in the + configuration of application startup is easier and provides + more features. Using the key words discussed in the rc.d section, - applications may now be set to start after certain other - services for example DNS; may permit extra - flags to be passed through rc.conf in - place of hard coded flags in the start up script, etc. A - basic script may look similar to the following: + applications can be set to start after certain other services + and extra flags can be passed through + /etc/rc.conf in place of hard coded flags + in the start up script. A basic script may look similar to + the following: #!/bin/sh # @@ -445,8 +431,8 @@ run_rc_command "$1" Using Services to Start Services - Other services, such as POP3 server - daemons, IMAP, etc. could be started using + Other services, such as the POP3 server + daemons or IMAP, could be started using &man.inetd.8;. This involves installing the service utility from the Ports Collection with a configuration line added to /etc/inetd.conf, or by @@ -487,14 +473,14 @@ run_rc_command "$1" configuration One of the most useful utilities in &os; is &man.cron.8;. - The cron utility runs in the background and - constantly checks the /etc/crontab file. - The cron utility also checks the - /var/cron/tabs directory, - in search of new crontab files. These - crontab files store information about - specific functions which cron is supposed to - perform at certain times. + This utility runs in the background and regularly checks + /etc/crontab for tasks to execute and + searches + /var/cron/tabs for custom + crontab files. These files store + information about specific functions which + cron is supposed to perform at certain + times. The cron utility uses two different types of configuration files, the system crontab and user crontabs. @@ -580,23 +566,22 @@ HOME=/var/log stands for day of the week. All these fields must be numeric values, and follow the twenty-four hour clock. The who field is special, and only exists in - the /etc/crontab file. This field - specifies which user the command should be run as. The last - field is the command to be executed. + /etc/crontab. This field specifies + which user the command should be run as. The last field is + the command to be executed. This last line will define the values discussed above. - Notice here we have a */5 listing, - followed by several more * characters. - These * characters mean + This example has a */5 listing,followed + by several more * characters. These + * characters mean first-last, and can be interpreted as - every time. So, judging by this line, - it is apparent that atrun is - to be invoked by root every five - minutes regardless of what day or month it is. For more - information on atrun, see - &man.atrun.8;. + every time. In this example, + atrun is invoked by + root every five minutes regardless of + the day or month. For more information on + atrun, refer to &man.atrun.8;. Commands can have any number of flags passed to them; however, commands which extend to multiple lines need to be @@ -606,8 +591,8 @@ HOME=/var/log This is the basic setup for every - crontab file, although there is one thing - different about this one. Field number six, where we specified + crontab, although there is one thing + different about this one. Field number six, which specifies the username, only exists in the system crontab. This field should be omitted for individual user crontab files. @@ -618,19 +603,18 @@ HOME=/var/log Do not use the procedure described here to edit and install the system crontab, - /etc/crontab. Just use your favorite - editor: the cron utility will notice that - the file has changed and immediately begin using the updated - version. See /etc/crontab. Instead, use an + editor: cron will notice that the file + has changed and immediately begin using the updated version. + See this FAQ entry for more information. To install a freshly written user - crontab, first use your favorite editor - to create a file in the proper format, and then use the - crontab utility. The most common usage - is: + crontab, first use an editor to create + and save a file in the proper format. Then, specify the file + name with crontab: &prompt.user; crontab crontab-file @@ -638,21 +622,18 @@ HOME=/var/log filename of a crontab that was previously created. - There is also an option to list installed - crontab files: just pass the - option to crontab and - look over the output. + To list installed crontab files, pass + to crontab. For users who wish to begin their own crontab file from scratch, without the use of a template, the crontab -e option is available. This will invoke the selected editor with an empty file. When the file - is saved, it will be automatically installed by the - crontab command. + is saved, it will be automatically installed by + crontab. In order to remove a user crontab - completely, use crontab with the - option. + completely, use crontab -r. @@ -700,13 +681,13 @@ HOME=/var/log the standard , and options will only perform their action if the appropriate /etc/rc.conf variables - are set. For instance the above sshd restart - command will only work if sshd_enable is set - to in /etc/rc.conf. + are set. For instance, sshd restart will + only work if sshd_enable is set to + in /etc/rc.conf. To , or a service regardless of the settings in /etc/rc.conf, the commands should be - prefixed with one. For instance to restart + prefixed with one. For instance, to restart sshd regardless of the current /etc/rc.conf setting, execute the following command: @@ -730,9 +711,9 @@ $sshd_enable=YES root console. - To determine if a service is running, a - option is available. For instance to - verify that sshd is actually started: + To determine if a service is running, use + . For instance, to verify that + sshd is running: &prompt.root; service sshd status sshd is running as pid 433. @@ -746,9 +727,9 @@ sshd is running as pid 433. The rc.d system is not only used for network services, it also contributes to most of the system - initialization. For instance, consider the - bgfsck file. When this script is executed, - it will print out the following message: + initialization. For instance, when the + bgfsck script is executed, it will print + out the following message: Starting background file system checks in 60 seconds. @@ -802,11 +783,10 @@ sshd is running as pid 433. systems. Additional information about the rc.d - system can be found in the &man.rc.8; and &man.rc.subr.8; manual - pages. If you are interested in writing your own - rc.d scripts or improving the existing - ones, you may find this - article also useful. + system can be found in &man.rc.8; and &man.rc.subr.8;. Refer to + this article for + instructions on how to create custom rc.d + scripts. @@ -828,9 +808,8 @@ sshd is running as pid 433. configuration - Nowadays we can not think about a computer without thinking - about a network connection. Adding and configuring a network - card is a common task for any &os; administrator. + Adding and configuring a network card is a common task for + any &os; administrator. Locating the Correct Driver @@ -840,28 +819,24 @@ sshd is running as pid 433. driver - Before you begin, you should know the model of the card - you have, the chip it uses, and whether it is a PCI or ISA - card. &os; supports a wide variety of both PCI and ISA cards. - Check the Hardware Compatibility List for your release to see - if your card is supported. + First, determine the model of the network interface card + and the chip it uses. &os; supports a wide variety of network + interface cards. Check the Hardware Compatibility List for + the &os; release to see if the card is supported. - Once you are sure your card is supported, you need to - determine the proper driver for the card. + If the card is supported, determine the name of the &os; + driver for the card. Refer to /usr/src/sys/conf/NOTES and /usr/src/sys/arch/conf/NOTES - will give you the list of network interface drivers with some - information about the supported chipsets/cards. If you have - doubts about which driver is the correct one, read the manual - page of the driver. The manual page will give you more - information about the supported hardware and even the possible - problems that could occur. - - If you own a common card, most of the time you will not - have to look very hard for a driver. Drivers for common - network cards are present in the GENERIC - kernel, so your card should show up during boot, like - so: + for the list of network interface drivers with some + information about the supported chipsets. When in doubt, read + the manual page of the driver as it will provide more + information about the supported hardware and any known + limitations of the driver. + + The drivers for common network cards are already present + in the GENERIC kernel, meaning the card + should show up during boot, as in this example: dc0: <82c169 PNIC 10/100BaseTX> port 0xa000-0xa0ff mem 0xd3800000-0xd38 000ff irq 15 at device 11.0 on pci0 @@ -878,19 +853,20 @@ bmtphy1: 10baseT, 10baseT-FDX, 100baseT dc1: Ethernet address: 00:a0:cc:da:da:db dc1: [ITHREAD] - In this example, we see that two cards using the - &man.dc.4; driver are present on the system. + In this example, two cards using the &man.dc.4; driver are + present on the system. - If the driver for your NIC is not present in - GENERIC, you will need to load the proper - driver to use your NIC. This may be accomplished in one of - two ways: + If the driver for the interface is not present in + GENERIC, but a driver is available, the + driver will need to be loaded before the interface can be + configured and used. This may be accomplished in one of two + ways: - The easiest way is to simply load a kernel module for - your network card with &man.kldload.8;, or automatically - at boot time by adding the appropriate line to the file + The easiest way is to load a kernel module for the + network card with &man.kldload.8;. To also automatically + load the driver at boot time, add the appropriate line to /boot/loader.conf. Not all NIC drivers are available as modules; notable examples of devices for which modules do not exist are ISA @@ -898,16 +874,15 @@ dc1: [ITHREAD] - Alternatively, you may statically compile the support - for your card into your kernel. Check + Alternatively, statically compile support for the card + into a custom kernel. Refer to /usr/src/sys/conf/NOTES, /usr/src/sys/arch/conf/NOTES - and the manual page of the driver to know what to add in - your kernel configuration file. For more information - about recompiling your kernel, please see - . If your card was detected - at boot by your kernel (GENERIC) you - do not have to build a new kernel. + and the manual page of the driver to determine which line + to add to the custom kernel configuration file. For more + information about recompiling the kernel, refer to + . If the card was detected + at boot, the kernel does not need to be recompiled. @@ -968,9 +943,9 @@ linuxemu/chapter.xml --> - Locate the files for your specific card. Generally, + Locate the files for the specific card. Generally, they can be found on the included CDs or at the vendor's - website. In the following examples, we will use + website. The following examples use W32DRIVER.SYS and W32DRIVER.INF. @@ -991,12 +966,12 @@ linuxemu/chapter.xml --> &prompt.root; kldload ./W32DRIVER_SYS.ko - In addition to the generated kernel module, you must - load the ndis.ko and - if_ndis.ko modules. This should be - automatically done when you load any module that depends on - &man.ndis.4;. If you want to load them manually, use the - following commands: + In addition to the generated kernel module, the + ndis.ko and + if_ndis.ko modules must be loaded. + This should happen automatically when any module that + depends on &man.ndis.4; is loaded. If not, load them + manually, using the following commands: &prompt.root; kldload ndis &prompt.root; kldload if_ndis @@ -1006,7 +981,7 @@ linuxemu/chapter.xml --> interface. Now, check &man.dmesg.8; to see if there were any errors - loading. If all went well, you should get output resembling + loading. If all went well, the output should be similar to the following: ndis0: <Wireless-G PCI Adapter> mem 0xf4100000-0xf4101fff irq 3 at device 8.0 on pci1 @@ -1019,9 +994,8 @@ ndis0: 11g rates: 6Mbps 9Mbps 12Mbps 18M ndis0 device like any other network interface (e.g., dc0). - You can configure the system to load the NDIS modules at - boot time in the same way as with any other module. First, - copy the generated module, + To configure the system to load the NDIS modules at + boot time, copy the generated module, W32DRIVER_SYS.ko, to the /boot/modules directory. Then, add the following line to @@ -1044,8 +1018,8 @@ ndis0: 11g rates: 6Mbps 9Mbps 12Mbps 18M network card may have been configured at installation time by sysinstall. - To display the configuration for the network interfaces on - your system, enter the following command: + To display the configuration for the network interfaces, + enter the following command: &prompt.user; ifconfig dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 @@ -1128,18 +1102,18 @@ lo0: flags=8049<UP,LOOPBACK,RUNNING,M The physical media selection is on autoselection mode (media: Ethernet autoselect (100baseTX - <full-duplex>)). We see that + <full-duplex>)). In this example, dc1 was configured to run with 10baseT/UTP media. For more - information on available media types for a driver, please - refer to its manual page. + information on available media types for a driver, refer + to its manual page. The status of the link (status) is - active, i.e., the carrier is detected. - For dc1, we see - status: no carrier. This is normal + active, indicating that the carrier is + detected. For dc1, the + status: no carrier status is normal when an Ethernet cable is not plugged into the card. @@ -1156,44 +1130,40 @@ lo0: flags=8049<UP,LOOPBACK,RUNNING,M it would indicate the card has not been configured. - To configure your card, you need root - privileges. The network card configuration can be done from - the command line with &man.ifconfig.8; but you would have to - do it after each reboot of the system. The file - /etc/rc.conf is where to add the network - card's configuration. - - Open /etc/rc.conf in your favorite - editor. You need to add a line for each network card present - on the system, for example in our case, we added these - lines: + To configure the card, you will need + root privileges. The network card + configuration can be performed from the command line with + &man.ifconfig.8; but will not persist after a reboot. + Instead, add the network card's configuration to + /etc/rc.conf using an editor. Add a + line for each network card present on the system, as seen in + this example: ifconfig_dc0="inet 192.168.1.3 netmask 255.255.255.0" ifconfig_dc1="inet 10.0.0.1 netmask 255.255.255.0 media 10baseT/UTP" - You have to replace dc0, - dc1, and so on, with the correct - device for your cards, and the addresses with the proper ones. - You should read the card driver and &man.ifconfig.8; manual - pages for more details about the allowed options and also - &man.rc.conf.5; manual page for more information on the syntax - of /etc/rc.conf. + Replace dc0 and + dc1 and the IP address information + with the correct values for the system. + Refer to the man page for the driver, &man.ifconfig.8; and + &man.rc.conf.5; for more details about the allowed options and + the syntax of /etc/rc.conf. - If you configured the network during installation, some + If the network was configured during installation, some lines about the network card(s) may be already present. Double check /etc/rc.conf before adding any lines. - You will also have to edit the file + If the network is not using DNS, edit /etc/hosts to add the names and the IP addresses of various machines of the LAN, if they are not - already there. For more information please refer to - &man.hosts.5; and to + already there. For more information, refer to &man.hosts.5; + and to /usr/share/examples/etc/hosts. - If access to the Internet is planned with the machine, - you also have to manually set up the default gateway and the + If there is no DHCP server and access to the Internet is + needed, manually configure the default gateway and the nameserver: &prompt.root; echo 'defaultrouter="your_default_router"' >> /etc/rc.conf @@ -1204,12 +1174,12 @@ ifconfig_dc1="inet 10.0.0.1 netmask 255. Testing and Troubleshooting - Once you have made the necessary changes in - /etc/rc.conf, you should reboot your - system. This will allow the change(s) to the interface(s) to - be applied, and verify that the system restarts without any - configuration errors. Alternatively you can just relaunch the - networking system: + Once the necessary changes in + /etc/rc.conf are saved, a reboot can be + used to test the network configuration and to verify that the + system restarts without any configuration errors. + Alternatively, apply the settings to the networking system + with this command: &prompt.root; service netif restart @@ -1221,8 +1191,8 @@ ifconfig_dc1="inet 10.0.0.1 netmask 255. &prompt.root; service routing restart - Once the networking system has been relaunched, you should - test the network interfaces. + Once the networking system has been relaunched, test the + network interfaces. Testing the Ethernet Card @@ -1233,10 +1203,8 @@ ifconfig_dc1="inet 10.0.0.1 netmask 255. To verify that an Ethernet card is configured correctly, - you have to try two things. First, ping the interface - itself, and then ping another machine on the LAN. - - First test the local interface: + ping the interface itself, and then ping another machine on + the LAN: &prompt.user; ping -c5 192.168.1.3 PING 192.168.1.3 (192.168.1.3): 56 data bytes @@ -1250,8 +1218,6 @@ PING 192.168.1.3 (192.168.1.3): 56 data 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.074/0.083/0.108/0.013 ms - Now we have to ping another machine on the LAN: - &prompt.user; ping -c5 192.168.1.2 PING 192.168.1.2 (192.168.1.2): 56 data bytes 64 bytes from 192.168.1.2: icmp_seq=0 ttl=64 time=0.726 ms @@ -1264,9 +1230,11 @@ PING 192.168.1.2 (192.168.1.2): 56 data 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms - You could also use the machine name instead of - 192.168.1.2 if you have set - up /etc/hosts. + To test network resolution, use the machine name instead + of 192.168.1.2. If there is + no DNS server on the network, + /etc/hosts must first be + configured. @@ -1279,30 +1247,29 @@ round-trip min/avg/max/stddev = 0.700/0. Troubleshooting hardware and software configurations is always a pain, and a pain which can be alleviated by - checking the simple things first. Is your network cable - plugged in? Have you properly configured the network - services? Did you configure the firewall correctly? Is the - card you are using supported by &os;? Always check the - hardware notes before sending off a bug report. Update your - version of &os; to the latest STABLE version. Check the - mailing list archives, or perhaps search the - Internet. + checking the simple things first. Is the network cable + plugged in? Are the network services properly configured? + Is the firewall configured correctly? Is the network card + supported by &os;? Always before sending a bug report, + check the hardware notes, update the version of &os; to the + latest STABLE version, check the mailing list archives, and + search the Internet. If the card works, yet performance is poor, it would be - worthwhile to read over the &man.tuning.7; manual page. You - can also check the network configuration as incorrect - network settings can cause slow connections. + worthwhile to read over the &man.tuning.7; manual page. + Also, check the network configuration as incorrect network + settings can cause slow connections. Some users experience one or two device timeout messages, which is normal for some cards. If they continue, or are bothersome, - you may wish to be sure the device is not conflicting with - another device. Double check the cable connections. - Perhaps you may just need to get another card. + determine if the device is conflicting with another device. + Double check the cable connections. Consider trying another + card. At times, users see a few watchdog timeout errors. The first - thing to do here is to check your network cable. Many cards + thing to do is to check the network cable. Many cards require a PCI slot which supports Bus Mastering. On some old motherboards, only one PCI slot allows it (usually slot 0). Check the network card and the motherboard @@ -1314,8 +1281,7 @@ round-trip min/avg/max/stddev = 0.700/0. host. This can happen if no default route is specified, or if a cable is unplugged. Check the output of netstat -rn and make sure there is a - valid route to the host you are trying to reach. If there - is not, read on to + valid route to the host. If there is not, read on to . ping: sendto: Permission denied @@ -1373,19 +1339,18 @@ round-trip min/avg/max/stddev = 0.700/0. For example, consider the case where the fxp0 interface is connected to two - networks, the 10.1.1.0 network + networks: the 10.1.1.0 network with a netmask of 255.255.255.0 and the 202.0.75.16 network with a netmask of 255.255.255.240. - We want the system to appear at + The system is to be configured to appear in the + range 10.1.1.1 through - 10.1.1.5 and at + 10.1.1.5 and 202.0.75.17 through - 202.0.75.20. As noted above, - only the first address in a given network range (in this case, - 10.0.1.1 and - 202.0.75.17) should have a real - netmask; all the rest (10.1.1.2 + 202.0.75.20. Only the first + address in a given network range should have a real + netmask. All the rest (10.1.1.2 through 10.1.1.5 and 202.0.75.18 through 202.0.75.20) must be configured @@ -1433,8 +1398,8 @@ ifconfig_fxp0_alias7="inet 202.0.75.20 n information to a system logging facility or other log file. - This section will describe how to configure and use the &os; - system logger, &man.syslogd.8;, as well as discuss log rotation + This section describes how to configure and use the &os; + system logger, &man.syslogd.8;, and how to perform log rotation and log management using &man.newsyslog.8;. Focus will be on setting up and using syslogd on a local machine. For more advanced setups using a separate @@ -1608,17 +1573,16 @@ cron.* Log files tend to grow quickly and accumulate steadily. This leads to the files being full of less immediately useful - information, as well as filling up the hard drive. To - mitigate this, log management comes into play. In &os;, - &man.newsyslog.8; is the tool used to manage log files. This - program is used to periodically rotate and compress log files, - as well as optionally create missing log files and signal - programs when log files are moved. The log files do not - necessarily have to come from syslog; &man.newsyslog.8; works - with any logs written from any program. It is important to - note that newsyslog is normally run from + information while filling up the hard drive. Log management + attempts to mitigate this. In &os;, &man.newsyslog.8; is used + to manage log files. This program periodically rotates and + compresses log files, and optionally creates missing log files + and signals programs when log files are moved. The log files + are not necessarily generated by syslog as &man.newsyslog.8; + works with any logs written from any program. Note that + newsyslog is normally run from &man.cron.8; and is not a system daemon. In the default - configuration it is run every hour. + configuration, it is run every hour. Configuring @@ -1629,11 +1593,10 @@ cron.* <filename>/etc/newsyslog.conf</filename>. This configuration file contains one line for each file that &man.newsyslog.8; manages. Each line states the file - owner, permissions, and when to rotate that file, as well as - optional flags that affect the log rotation (such as - compression) and programs to signal when the log is - rotated. As an example, here is the default configuration - in &os;:</para> + owner, permissions, when to rotate that file, optional flags + that affect log rotation, such as compression, and programs + to signal when the log is rotated. Here is the default + configuration in &os;:</para> <programlisting># configuration file for newsyslog # $&os;$ @@ -1676,7 +1639,7 @@ cron.* /var/log/xferlog 600 7 100 * JC</programlisting> <para>Each line starts with the name of the file to be - rotated, optionally followrd by an owner + rotated, optionally followed by an owner and group for both rotated and newly created files. The next field, <literal>mode</literal> is the mode of the files and <literal>count</literal> denotes how many rotated @@ -1841,7 +1804,7 @@ nameserver 147.11.100.30</programlisting <literal>domain</literal> options should be used.</para> </note> - <para>If you are using DHCP, &man.dhclient.8; usually rewrites + <para>When using DHCP, &man.dhclient.8; usually rewrites <filename>resolv.conf</filename> with information received from the DHCP server.</para> </sect3> @@ -1943,12 +1906,12 @@ security.bsd.see_other_uids=0</programli <secondary>with sysctl</secondary> </indexterm> - <para>&man.sysctl.8; is an interface that allows you to make - changes to a running &os; system. This includes many advanced - options of the TCP/IP stack and virtual memory system that can - dramatically improve performance for an experienced system - administrator. Over five hundred system variables can be read - and set using &man.sysctl.8;.</para> + <para>&man.sysctl.8; is used to make changes to a running &os; + system. This includes many advanced options of the TCP/IP stack + and virtual memory system that can dramatically improve + performance for an experienced system administrator. Over five + hundred system variables can be read and set using + &man.sysctl.8;.</para> <para>At its core, &man.sysctl.8; serves two functions: to read and to modify system settings.</para> @@ -1974,11 +1937,10 @@ kern.maxfiles: 2088 -> 5000</screen> numbers, or booleans (a boolean being <literal>1</literal> for yes or a <literal>0</literal> for no).</para> - <para>If you want to automatically set some variables each time - the machine boots, add them to - <filename>/etc/sysctl.conf</filename>. For more - information see the &man.sysctl.conf.5; manual page and - <xref linkend="configtuning-sysctlconf"/>.</para> + <para>To automatically set some variables each time the machine + boots, add them to <filename>/etc/sysctl.conf</filename>. For + more information refer to &man.sysctl.conf.5; and <xref + linkend="configtuning-sysctlconf"/>.</para> <sect2 id="sysctl-readonly"> <sect2info> @@ -2039,15 +2001,15 @@ device_probe_and_attach: cbb0 attach ret fragment (typically 1 K) in the file system and less (typically 512 bytes) in the buffer cache. With this variable turned off (to 0), the buffer cache will only cache - a fixed number of directories even if you have a huge amount - of memory. When turned on (to 1), this sysctl allows the - buffer cache to use the VM Page Cache to cache the + a fixed number of directories even if the system has a huge + amount of memory. When turned on (to 1), this sysctl allows + the buffer cache to use the VM Page Cache to cache the directories, making all the memory available for caching directories. However, the minimum in-core memory used to cache a directory is the physical page size (typically - 4 K) rather than 512  bytes. We recommend keeping - this option on if you are running any services which - manipulate large numbers of files. Such services can + 4 K) rather than 512  bytes. Keeping this option + enabled is recommended if the system is running any services + which manipulate large numbers of files. Such services can include web caches, large mail systems, and news systems. Keeping this option on will generally not reduce performance even with the wasted memory but you should experiment to @@ -2067,8 +2029,8 @@ device_probe_and_attach: cbb0 attach ret which typically occurs when writing large sequential files. The idea is to avoid saturating the buffer cache with dirty buffers when it would not benefit I/O performance. However, - this may stall processes and under certain circumstances you - may wish to turn it off.</para> + this may stall processes and under certain circumstances + should be turned off.</para> </sect3> <sect3> @@ -2082,17 +2044,17 @@ device_probe_and_attach: cbb0 attach ret variable determines how much outstanding write I/O may be queued to disk controllers system-wide at any given instance. The default is usually sufficient but on machines - with lots of disks you may want to bump it up to four or - five <emphasis>megabytes</emphasis>. Note that setting too + with lots of disks, try bumping it up to four or five + <emphasis>megabytes</emphasis>. Note that setting too high a value (exceeding the buffer cache's write threshold) can lead to extremely bad clustering performance. Do not set this value arbitrarily high! Higher write values may add latency to reads occurring at the same time.</para> <para>There are various other buffer-cache and VM page cache - related sysctls. We do not recommend modifying these - values, the VM system does an extremely good job of - automatically tuning itself.</para> *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-all@FreeBSD.ORG Tue Feb 12 20:36:47 2013 Return-Path: <owner-svn-doc-all@FreeBSD.ORG> Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 6B2E4B88; Tue, 12 Feb 2013 20:36:47 +0000 (UTC) (envelope-from brd@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 5DA0BF7D; Tue, 12 Feb 2013 20:36:47 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1CKakGq075002; Tue, 12 Feb 2013 20:36:46 GMT (envelope-from brd@svn.freebsd.org) Received: (from brd@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1CKaklA075001; Tue, 12 Feb 2013 20:36:46 GMT (envelope-from brd@svn.freebsd.org) Message-Id: <201302122036.r1CKaklA075001@svn.freebsd.org> From: Brad Davis <brd@FreeBSD.org> Date: Tue, 12 Feb 2013 20:36:46 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40960 - head/en_US.ISO8859-1/htdocs/releng X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" <svn-doc-all.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-all> List-Post: <mailto:svn-doc-all@freebsd.org> List-Help: <mailto:svn-doc-all-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 12 Feb 2013 20:36:47 -0000 Author: brd Date: Tue Feb 12 20:36:46 2013 New Revision: 40960 URL: http://svnweb.freebsd.org/changeset/doc/40960 Log: - Add a mention of the upcoming 8.4 Approved by: re (jpaetzel) Modified: head/en_US.ISO8859-1/htdocs/releng/index.xml Modified: head/en_US.ISO8859-1/htdocs/releng/index.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/releng/index.xml Tue Feb 12 15:13:12 2013 (r40959) +++ head/en_US.ISO8859-1/htdocs/releng/index.xml Tue Feb 12 20:36:46 2013 (r40960) @@ -51,8 +51,14 @@ <tr> <td>TBD</td> + <td>&os; 8.4</td> + <td><!-- <a href="&base;/releases/8.4R/schedule.html">Target Schedule</a> --></td> + </tr> + + <tr> + <td>TBD</td> <td>&os; 9.2</td> - <td><!-- <a href="&base;/releases/9.1R/schedule.html">Target Schedule</a> --></td> + <td><!-- <a href="&base;/releases/9.2R/schedule.html">Target Schedule</a> --></td> </tr> </table> From owner-svn-doc-all@FreeBSD.ORG Tue Feb 12 23:00:21 2013 Return-Path: <owner-svn-doc-all@FreeBSD.ORG> Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4CE3FF70; Tue, 12 Feb 2013 23:00:21 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-5.mit.edu (DMZ-MAILSEC-SCANNER-5.MIT.EDU [18.7.68.34]) by mx1.freebsd.org (Postfix) with ESMTP id 96F59937; Tue, 12 Feb 2013 23:00:20 +0000 (UTC) X-AuditID: 12074422-b7f5c6d000000545-0f-511ac850d281 Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) by dmz-mailsec-scanner-5.mit.edu (Symantec Messaging Gateway) with SMTP id E9.A6.01349.058CA115; Tue, 12 Feb 2013 17:55:12 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id r1CMtCN9027875; Tue, 12 Feb 2013 17:55:12 -0500 Received: from multics.mit.edu (SYSTEM-LOW-SIPB.MIT.EDU [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id r1CMtAu8015225 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 12 Feb 2013 17:55:11 -0500 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id r1CMt9xa008907; Tue, 12 Feb 2013 17:55:09 -0500 (EST) Date: Tue, 12 Feb 2013 17:55:09 -0500 (EST) From: Benjamin Kaduk <kaduk@MIT.EDU> To: Dru Lavigne <dru@freebsd.org> Subject: Re: svn commit: r40959 - head/en_US.ISO8859-1/books/handbook/config In-Reply-To: <201302121513.r1CFDCBh075489@svn.freebsd.org> Message-ID: <alpine.GSO.1.10.1302121741430.9389@multics.mit.edu> References: <201302121513.r1CFDCBh075489@svn.freebsd.org> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrHIsWRmVeSWpSXmKPExsUixCmqrRtwQirQoG2SocWPj4eYLLqaVC1u LNrPZLG7v5fZgcVjxqf5LAGMUVw2Kak5mWWpRfp2CVwZvXeeMRasEatYc2YnYwNjg1AXIweH hICJxKb/5V2MnECmmMSFe+vZuhi5OIQE9jFKNJx7zA7hbGSUmHt7PlTmEJPEozs/WCCcBkaJ m0++soKMYhHQljg3MxZkFJuAisTMNxvZQGwRAUWJp1/3MoLYzAJREnuWNrKC2MICfhI35x5g AmnlFLCS2NElDBLmFXCQOLz2NQtIWEjAUuLlziqQsKiAjsTq/VNYIEoEJU7OfMICMdFS4t/a X6wTGAVnIUnNQpJawMi0ilE2JbdKNzcxM6c4NVm3ODkxLy+1SNdULzezRC81pXQTIyhY2V2U djD+PKh0iFGAg1GJh9chRCpQiDWxrLgy9xCjJAeTkihv5HGgEF9SfkplRmJxRnxRaU5q8SFG CQ5mJRHeB3uBcrwpiZVVqUX5MClpDhYlcd5rKTf9hQTSE0tSs1NTC1KLYLIyHBxKErypIEMF i1LTUyvSMnNKENJMHJwgw3mAhreC1PAWFyTmFmemQ+RPMSpKifNyHwVKCIAkMkrz4HphyeQV ozjQK8K8XiDtPMBEBNf9CmgwE9BgxrVgg0sSEVJSDYyF9bP/qp/YVjf54Z1drZdf5z76bH4j gfdCXrUJx+S0qSsSZz06areTMe+8+ETpixyz1n8rfiS9TDvvh8MpfmkzzaQaHpFJF7+WKKto H3P/obk4K1RyRdJW3s1e6w0TDx7/KX6LR/RJ5GnHjdevKCxR27OHg8+Gr3l+4RGLPM4tRzYd 01e9JpWjxFKckWioxVxUnAgAxshdpQEDAAA= Cc: svn-doc-head@freebsd.org, svn-doc-all@freebsd.org, doc-committers@freebsd.org X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" <svn-doc-all.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-all> List-Post: <mailto:svn-doc-all@freebsd.org> List-Help: <mailto:svn-doc-all-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 12 Feb 2013 23:00:21 -0000 On Tue, 12 Feb 2013, Dru Lavigne wrote: > Modified: head/en_US.ISO8859-1/books/handbook/config/chapter.xml > ============================================================================== > --- head/en_US.ISO8859-1/books/handbook/config/chapter.xml Tue Feb 12 15:09:50 2013 (r40958) > +++ head/en_US.ISO8859-1/books/handbook/config/chapter.xml Tue Feb 12 15:13:12 2013 (r40959) > @@ -730,9 +711,9 @@ $sshd_enable=YES</screen> > <username>root</username> console.</para> > </note> > > - <para>To determine if a service is running, a > - <option>status</option> option is available. For instance to > - verify that <command>sshd</command> is actually started:</para> > + <para>To determine if a service is running, use I might use "whether" instead of "if"; not sure. > + <option>status</option>. For instance, to verify that > + <command>sshd</command> is running:</para> > > <screen>&prompt.root; <userinput>service sshd status</userinput> > sshd is running as pid 433.</screen> > @@ -1128,18 +1102,18 @@ lo0: flags=8049<UP,LOOPBACK,RUNNING,M > > <listitem> > <para>The status of the link (<literal>status</literal>) is > - <literal>active</literal>, i.e., the carrier is detected. > - For <devicename>dc1</devicename>, we see > - <literal>status: no carrier</literal>. This is normal > + <literal>active</literal>, indicating that the carrier is I think this would be better as "carrier signal". > + detected. For <devicename>dc1</devicename>, the > + <literal>status: no carrier</literal> status is normal > when an Ethernet cable is not plugged into the > card.</para> > </listitem> > @@ -1156,44 +1130,40 @@ lo0: flags=8049<UP,LOOPBACK,RUNNING,M > > <para>it would indicate the card has not been configured.</para> > > + <para>To configure the card, you will need > + <username>root</username> privileges. The network card > + configuration can be performed from the command line with > + &man.ifconfig.8; but will not persist after a reboot. > + Instead, add the network card's configuration to Changes to rc.conf will not necessarily take effect immediately, and I don't know/remember exactly what conditions cause settings in rc.conf to be read. Cloned wlan device configurations take effect on creation, but I don't know about fixed devices. Maybe it is also on device probe/creation time. In any case, the point is that this is not really an "instead" thing, more an "in addition" thing. Hmm, this is sort of covered in "Testing and Troubleshooting", below. > + <filename>/etc/rc.conf</filename> using an editor. Add a > + line for each network card present on the system, as seen in > + this example:</para> > > *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** Oops. -Ben From owner-svn-doc-all@FreeBSD.ORG Wed Feb 13 02:56:36 2013 Return-Path: <owner-svn-doc-all@FreeBSD.ORG> Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E216EB99; Wed, 13 Feb 2013 02:56:36 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id D40FB3DB; Wed, 13 Feb 2013 02:56:36 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1D2uahU089599; Wed, 13 Feb 2013 02:56:36 GMT (envelope-from linimon@svn.freebsd.org) Received: (from linimon@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1D2uaoP089598; Wed, 13 Feb 2013 02:56:36 GMT (envelope-from linimon@svn.freebsd.org) Message-Id: <201302130256.r1D2uaoP089598@svn.freebsd.org> From: Mark Linimon <linimon@FreeBSD.org> Date: Wed, 13 Feb 2013 02:56:36 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40961 - head/en_US.ISO8859-1/articles/portbuild X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" <svn-doc-all.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-all> List-Post: <mailto:svn-doc-all@freebsd.org> List-Help: <mailto:svn-doc-all-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 13 Feb 2013 02:56:37 -0000 Author: linimon Date: Wed Feb 13 02:56:35 2013 New Revision: 40961 URL: http://svnweb.freebsd.org/changeset/doc/40961 Log: Add the contents of portbuild/tools/example_install as an example of how to quickly install portbuild. Modified: head/en_US.ISO8859-1/articles/portbuild/article.xml Modified: head/en_US.ISO8859-1/articles/portbuild/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/portbuild/article.xml Tue Feb 12 20:36:46 2013 (r40960) +++ head/en_US.ISO8859-1/articles/portbuild/article.xml Wed Feb 13 02:56:35 2013 (r40961) @@ -2462,9 +2462,6 @@ zfs destroy -r a/snap/src-<replaceable>o jails.</para> </listitem> </itemizedlist> - - <para>This document has not yet been updated with the latest changes. - </para> </sect2> <sect2 id="pointyhat-basics"> @@ -2482,12 +2479,6 @@ zfs destroy -r a/snap/src-<replaceable>o </step> <step> - <para>Export that value for a later initialization step:</para> - - <screen>&prompt.root; export PORTBUILD_USER=<replaceable>portbuild</replaceable></screen> - </step> - - <step> <para>Similarly, create a user to own the administration functions and manage the <application>svn</application> repositories, such as <literal>srcbuild</literal>. It should have the @@ -2495,12 +2486,6 @@ zfs destroy -r a/snap/src-<replaceable>o </step> <step> - <para>Export that value for a later initialization step:</para> - - <screen>&prompt.root; export SRCBUILD_USER=<replaceable>srcbuild</replaceable></screen> - </step> - - <step> <para>Add the following to <filename>/boot/loader.conf</filename>:</para> <programlisting>console="vidconsole,comconsole"</programlisting> @@ -2644,8 +2629,57 @@ sysutils/zfs-stats</programlisting> <para>The following steps need to be done as euid root.</para> + <para>Here is a quick example:</para> + + <example> + <title>The contents of example file <filename>portbuild/tools/example_install</filename> + + +#!/bin/sh +# +# example script to drive the "mkportbuild" kickstart file +# +export PORTBUILD_USER=portbuild +export SRCBUILD_USER=srcbuild +export ZFS_VOLUME=a +export ZFS_MOUNTPOINT=/a +export VCS_REPOSITORY=svn://svn0.us-east.FreeBSD.org + +# +# create the zpool. the examples here are just suggestions and need to be +# customized for your site. +# +# simple examples: +# zpool create ${ZFS_VOLUME} da1 +# zpool create ${ZFS_VOLUME} gprootfs +# more complex example: +# zpool create ${ZFS_VOLUME} mirror da1 da2 mirror da3 da4 mirror da5 da6 mirror da7 da8 + +# +# check out the kickstart file and run it +# +mkdir -p tmp +svn checkout ${VCS_REPOSITORY}/base/projects/portbuild/admin/tools tmp +sh -x ./tmp/mkportbuild + + + + Here is a detailed explanation of the example: + + Export the value of PORTBUILD_USER: + + &prompt.root; export PORTBUILD_USER=portbuild + + + + Export the value of SRCBUILD_USER: + + &prompt.root; export SRCBUILD_USER=srcbuild + + + Pick a zfs volume name and export it. We have used a so far to date. @@ -2670,9 +2704,11 @@ sysutils/zfs-stats - We will define a zfs - permission set below, so that the - srcbuild user may administer this + The kickstart script defines zfs + permission sets, so that the + srcbuild user and + portbuild user may administer + subdirectories of this volume without having to have root privileges. @@ -2890,7 +2926,7 @@ sysutils/zfs-stats - Copy the following files from + As root, copy the following files from /a/portbuild/admin/etc/rc.d/ to /usr/local/etc/rc.d/: From owner-svn-doc-all@FreeBSD.ORG Wed Feb 13 05:11:17 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 6DC1D9CA; Wed, 13 Feb 2013 05:11:17 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 60686AD4; Wed, 13 Feb 2013 05:11:17 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1D5BHAM032058; Wed, 13 Feb 2013 05:11:17 GMT (envelope-from linimon@svn.freebsd.org) Received: (from linimon@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1D5BHTV032057; Wed, 13 Feb 2013 05:11:17 GMT (envelope-from linimon@svn.freebsd.org) Message-Id: <201302130511.r1D5BHTV032057@svn.freebsd.org> From: Mark Linimon Date: Wed, 13 Feb 2013 05:11:17 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40962 - head/en_US.ISO8859-1/articles/portbuild X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Feb 2013 05:11:17 -0000 Author: linimon Date: Wed Feb 13 05:11:16 2013 New Revision: 40962 URL: http://svnweb.freebsd.org/changeset/doc/40962 Log: Move SUPPORTED_ARCHS to admin/conf/admin.conf. Modified: head/en_US.ISO8859-1/articles/portbuild/article.xml Modified: head/en_US.ISO8859-1/articles/portbuild/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/portbuild/article.xml Wed Feb 13 02:56:35 2013 (r40961) +++ head/en_US.ISO8859-1/articles/portbuild/article.xml Wed Feb 13 05:11:16 2013 (r40962) @@ -2788,6 +2788,11 @@ sh -x ./tmp/mkportbuild + Set SUPPORTED_ARCHS to the + list of architectures you wish to build packages for. + + + For each source branch you will be building for, set SRC_BRANCHES and SRC_BRANCH_branch_SUBDIR @@ -2862,11 +2867,6 @@ sh -x ./tmp/mkportbuild /a/portbuild/conf/server.conf: - - Set SUPPORTED_ARCHS to the - list of architectures you wish to build packages for. - - - This inventory file typically lives in - i386/${branch} - on the cluster master. - - This is useful to aid in periodically cleaning out + You should use that output to periodically clean out the distfiles from ftp-master. When space gets tight, distfiles from recent releases can be kept while others can be thrown away. @@ -1047,6 +1042,16 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 Uploading Packages + + For FreeBSD.org as of 2013, the instructions + about uploading to ftp-master are obsolete. + In the future, ftp-master will pull + from pointyhat, using a mechanism yet + to be implemented. However, the instructions about + RESTRICTED and NO_CDROM + must still be carefully followed. + + Once a build has completed, packages and/or distfiles can be transferred to ftp-master for propagation to the FTP mirror network. If the build was @@ -1124,7 +1129,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 a new release), copy packages to the staging area on ftp-master with something like the following: - &prompt.root; cd /var/portbuild/${arch}/${branch} + &prompt.root; cd /a/portbuild/${arch}/${branch} &prompt.root; tar cfv - packages/ | ssh portmgr@ftp-master tar xfC - w/ports/${arch}/tmp/${subdir} Then log into ftp-master, verify that @@ -1152,7 +1157,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 Distfiles should be transferred with the cpdistfiles script: - &prompt.root; /var/portbuild/scripts/cpdistfiles ${arch} ${branch} ${buildid} [-yesreally] | tee log2 + &prompt.root; /a/portbuild/scripts/cpdistfiles ${arch} ${branch} ${buildid} [-yesreally] | tee log2 Doing it by hand is deprecated. @@ -1160,6 +1165,11 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 Experimental Patches Builds + + Most of the information in this section is obsolete + as of 2013. + + Experimental patches builds are run from time to time to new features or bugfixes to the ports infrastructure (i.e. bsd.port.mk), or to test large sweeping @@ -1210,12 +1220,6 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 build. This will ensure an apples-to-apples comparison later. - - Once the build finishes, compare the control build failures to those of the experimental patches build. Use the following commands to facilitate this (this assumes the 8 @@ -1300,9 +1304,9 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 The following command will set up the control branch for - the partial build (old codebase): + the partial build: - &prompt.user; /var/portbuild/scripts/dopackages.8 -noportsvcs -nobuild -novcs -nofinish + &prompt.user; /a/portbuild/scripts/dopackages.wrapper 8 -noportsvcs -nobuild -novcs -nofinish The builds must be performed from the @@ -1317,7 +1321,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 <#> is the concurrency of the build to attempt. It is usually the sum of the weights listed in - /var/portbuild/i386/mlist unless you have a + /a/portbuild/i386/mlist unless you have a reason to run a heavier or lighter build. The list of packages to build should be a list of package @@ -1350,17 +1354,15 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 Before following these steps, please coordinate with portmgr. - - Due to some generous donations, portmgr is - no longer looking for the loan of &i386; or amd64 - systems. However, we are still interested in borrowing tier-2 - systems. - - Node requirements - portmgr is still working on characterizing + + This section is only of interest when considering + tier-2 architectures. + + + Here are the requirement for what a node needs to be generally useful. @@ -1440,7 +1442,8 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 /usr2/.) The filename chroot is a - historical remnant. + historical remnant. The chroot + command is no longer used. @@ -1481,8 +1484,9 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 Generate a kernel config file. Include - GENERIC (or, if you are using more than - 3.5G on &i386;, PAE). + GENERIC (or, if on &i386, and + you are using more than + 3.5G, PAE). Required options: @@ -1497,9 +1501,14 @@ options SHMMAXPGS=65536 options SEMMNI=40 options SEMMNS=240 options SEMUME=40 -options SEMMNU=120 +options SEMMNU=120 + + If you are interested in debugging general + problems, you may wish to use the following. + However, for unattended operations, it is best + to leave it out: -options ALT_BREAK_TO_DEBUGGER + options ALT_BREAK_TO_DEBUGGER For PAE, it is not currently possible to load modules. Therefore, if you are running an architecture @@ -1916,7 +1925,7 @@ portbuild ALL=(ALL) NOPASSWD: ALL

Create - /var/portbuild/${arch}/clients/bindist-${hostname}.tar. + /a/portbuild/${arch}/clients/bindist-${hostname}.tar. @@ -1955,16 +1964,16 @@ MASTER_SITE_OVERRIDE= \ Hint: you will need one of these for each machine; however, if you have multiple machines at one site, you should create a site-specific one (e.g., in - /var/portbuild/conf/clients/) + /a/portbuild/conf/clients/) and symlink to it. Create -/var/portbuild/${arch}/portbuild-${hostname} +/a/portbuild/${arch}/portbuild-${hostname} using one of the existing ones as a guide. This file contains overrides to -/var/portbuild/${arch}/portbuild.conf. +/a/portbuild/${arch}/portbuild.conf. Suggested values: @@ -2030,7 +2039,7 @@ ssh_cmd="/usr/local/bin/ssh" Populate the client's copy of /var/portbuild/scripts/ by something like - /var/portbuild/scripts/dosetupnode arch major latest hostname. + /a/portbuild/scripts/dosetupnode arch major latest hostname. Verify that you now have files in that directory. @@ -2075,7 +2084,7 @@ ssh_cmd="/usr/local/bin/ssh"Once you are sure that the client is working, tell pollmachine about it by adding it to - /var/portbuild/${arch}/mlist. + /a/portbuild/${arch}/mlist. From owner-svn-doc-all@FreeBSD.ORG Fri Feb 15 14:53:39 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4F9BEB5B; Fri, 15 Feb 2013 14:53:39 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 3D543146; Fri, 15 Feb 2013 14:53:39 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1FErdRR085512; Fri, 15 Feb 2013 14:53:39 GMT (envelope-from linimon@svn.freebsd.org) Received: (from linimon@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1FErd6W085511; Fri, 15 Feb 2013 14:53:39 GMT (envelope-from linimon@svn.freebsd.org) Message-Id: <201302151453.r1FErd6W085511@svn.freebsd.org> From: Mark Linimon Date: Fri, 15 Feb 2013 14:53:39 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40974 - head/en_US.ISO8859-1/articles/portbuild X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Feb 2013 14:53:39 -0000 Author: linimon Date: Fri Feb 15 14:53:38 2013 New Revision: 40974 URL: http://svnweb.freebsd.org/changeset/doc/40974 Log: Move the privsep section up to the top of the document. No textaul change. Modified: head/en_US.ISO8859-1/articles/portbuild/article.xml Modified: head/en_US.ISO8859-1/articles/portbuild/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/portbuild/article.xml Fri Feb 15 14:49:56 2013 (r40973) +++ head/en_US.ISO8859-1/articles/portbuild/article.xml Fri Feb 15 14:53:38 2013 (r40974) @@ -158,6 +158,51 @@ found in CVS. + + + Notes on privilege separation + + As of January 2013, a rewrite is in progress to further separate + privileges. The following concepts are introduced: + + + + Server-side user portbuild assumes all + responsiblity for operations involving builds and communicating + with the clients. This user no longer has access to + sudo. + + + + Server-side user srcbuild is created + and given responsiblity for operations involving both VCS + operations and anything involving src builds for the clients. + This user does not have access to + sudo. + + + + The server-side + ports-arch + users go away. + + + + None of the above server-side users have + ssh keys. Individual + portmgr will accomplish all those + tasks using ksu. (This is + still work-in-progress.) + + + + The only client-side user is also named + portbuild and still has access to + sudo for the purpose of managing + jails. + + + @@ -2428,51 +2473,6 @@ zfs destroy -r a/snap/src-o Please talk to Mark Linimon before making any changes to this section. - - Notes on privilege separation - - As of January 2013, a rewrite is in progress to further separate - privileges. The following concepts are introduced: - - - - Server-side user portbuild assumes all - responsiblity for operations involving builds and communicating - with the clients. This user no longer has access to - sudo. - - - - Server-side user srcbuild is created - and given responsiblity for operations involving both VCS - operations and anything involving src builds for the clients. - This user does not have access to - sudo. - - - - The server-side - ports-arch - users go away. - - - - None of the above server-side users have - ssh keys. Individual - portmgr will accomplish all those - tasks using ksu. (This is - still work-in-progress.) - - - - The only client-side user is also named - portbuild and still has access to - sudo for the purpose of managing - jails. - - - - Basic installation From owner-svn-doc-all@FreeBSD.ORG Fri Feb 15 15:05:38 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E20C6D0; Fri, 15 Feb 2013 15:05:38 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id C49551CE; Fri, 15 Feb 2013 15:05:38 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1FF5c7R089158; Fri, 15 Feb 2013 15:05:38 GMT (envelope-from linimon@svn.freebsd.org) Received: (from linimon@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1FF5coU089157; Fri, 15 Feb 2013 15:05:38 GMT (envelope-from linimon@svn.freebsd.org) Message-Id: <201302151505.r1FF5coU089157@svn.freebsd.org> From: Mark Linimon Date: Fri, 15 Feb 2013 15:05:38 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40975 - head/en_US.ISO8859-1/articles/portbuild X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Feb 2013 15:05:39 -0000 Author: linimon Date: Fri Feb 15 15:05:38 2013 New Revision: 40975 URL: http://svnweb.freebsd.org/changeset/doc/40975 Log: Clarify that some information is specific to connected nodes. While here, do some other cleanup. Modified: head/en_US.ISO8859-1/articles/portbuild/article.xml Modified: head/en_US.ISO8859-1/articles/portbuild/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/portbuild/article.xml Fri Feb 15 14:53:38 2013 (r40974) +++ head/en_US.ISO8859-1/articles/portbuild/article.xml Fri Feb 15 15:05:38 2013 (r40975) @@ -831,7 +831,7 @@ PKG_BIN=/usr/local/sbin/pkgTo free up resources, you will need to clean up client machines by running build cleanup command. For example: - &prompt.user; /var/portbuild/scripts/build cleanup i386 8-exp 20080714120411 -full + &prompt.user; /a/portbuild/scripts/build cleanup i386 8-exp 20080714120411 -full If you forget to do this, then the old build jails will not be cleaned up for 24 hours, and no @@ -846,6 +846,11 @@ PKG_BIN=/usr/local/sbin/pkgloads thinks are in use, you are in trouble. + + The following notes about mounting only apply to + connected nodes. + + You may have problem with the umount commands hanging. If so, you are going to have to use the allgohans script to run an &man.ssh.1; @@ -875,6 +880,11 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 You may also see messages about procfs. + + The above is the end of the notes that apply only to + connected nodes. + + After you have done all the above, remove the ${arch}/lock file before trying to restart the build. If you do not, @@ -921,7 +931,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 scripts/stats ${branch} command shows the number of packages already built. - Running cat /var/portbuild/*/loads/* + Running cat /a/portbuild/*/loads/* shows the client loads and number of concurrent builds in progress. The files that have been recently updated are the clients that are online; the others are the offline clients. @@ -958,7 +968,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 it if not. Keep an eye on &man.df.1; output. If the - /var/portbuild file system becomes full + /a/portbuild file system becomes full then Bad Things happen. The status of all current builds is generated periodically @@ -1212,7 +1222,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 Most of the information in this section is obsolete - as of 2013. + as of 2013 and needs to be rewritten. Experimental patches builds are run from time to time to @@ -1271,9 +1281,9 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 branch is the control branch, and the 8-exp branch is the experimental patches branch): - &prompt.user; cd /var/portbuild/i386/8-exp/errors + &prompt.user; cd /a/portbuild/i386/8-exp/errors &prompt.user; find . -name \*.log\* | sort > /tmp/8-exp-errs -&prompt.user; cd /var/portbuild/i386/8/errors +&prompt.user; cd /a/portbuild/i386/8/errors &prompt.user; find . -name \*.log\* | sort > /tmp/8-errs @@ -1336,7 +1346,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 rebuild of the affected packages under the control branch: - &prompt.user; cd /var/portbuild/i386/8/ports + &prompt.user; cd /a/portbuild/i386/8/ports The following example is obsolete @@ -1351,7 +1361,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 The following command will set up the control branch for the partial build: - &prompt.user; /a/portbuild/scripts/dopackages.wrapper 8 -noportsvcs -nobuild -novcs -nofinish + &prompt.user; /a/portbuild/scripts/dopackages.wrapper i386 8 -noportsvcs -nobuild -novcs -nofinish The builds must be performed from the @@ -1359,7 +1369,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5 initially be empty except for the Makefile symlink. If this symlink does not exist, it must be created: - &prompt.user; cd /var/portbuild/i386/8/packages/All + &prompt.user; cd /a/portbuild/i386/8/packages/All &prompt.user; ln -sf ../../Makefile . &prompt.user; make -k -j<#> <list of packages to build> @@ -3072,7 +3082,7 @@ qmanager Note the time and failure mode (e.g., paste in the relevant console output) in - /var/portbuild/${arch}/reboots + /a/portbuild/${arch}/reboots From owner-svn-doc-all@FreeBSD.ORG Fri Feb 15 22:47:36 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id EAB737E; Fri, 15 Feb 2013 22:47:36 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id DBA39B11; Fri, 15 Feb 2013 22:47:36 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1FMlaos029984; Fri, 15 Feb 2013 22:47:36 GMT (envelope-from ryusuke@svn.freebsd.org) Received: (from ryusuke@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1FMlaTl029983; Fri, 15 Feb 2013 22:47:36 GMT (envelope-from ryusuke@svn.freebsd.org) Message-Id: <201302152247.r1FMlaTl029983@svn.freebsd.org> From: Ryusuke SUZUKI Date: Fri, 15 Feb 2013 22:47:36 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40976 - head/ja_JP.eucJP/books/handbook/ports X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Feb 2013 22:47:37 -0000 Author: ryusuke Date: Fri Feb 15 22:47:36 2013 New Revision: 40976 URL: http://svnweb.freebsd.org/changeset/doc/40976 Log: - Merge the following from the English version: r40554 -> r40855 head/ja_JP.eucJP/books/handbook/ports/chapter.xml Modified: head/ja_JP.eucJP/books/handbook/ports/chapter.xml Modified: head/ja_JP.eucJP/books/handbook/ports/chapter.xml ============================================================================== --- head/ja_JP.eucJP/books/handbook/ports/chapter.xml Fri Feb 15 15:05:38 2013 (r40975) +++ head/ja_JP.eucJP/books/handbook/ports/chapter.xml Fri Feb 15 22:47:36 2013 (r40976) @@ -3,7 +3,7 @@ The FreeBSD Documentation Project The FreeBSD Japanese Documentation Project - Original revision: r40554 + Original revision: r40855 $FreeBSD$ --> @@ -15,14 +15,15 @@ ports packages - FreeBSD の基本システムには数多くのシステムツールが含まれています。 + &os; の基本システムには数多くのシステムツールが含まれています。 しかしながら、サードパーティ製のアプリケーションをインストールしないと、 実用的にはそれほどたくさんのことはできません。 - FreeBSD は、サードパーティ製のソフトウェアの導入を支援するために、 + &os; は、サードパーティ製のソフトウェアの導入を支援するために、 ソースコードをコンパイルしてインストールする Ports Collection と、 コンパイル済みのバイナリをインストールする packages という相補的な 2 つの技術を提供しています。 - どちらのシステムを用いても、ローカルメディアやネットワーク上からお気に入りのアプリケーションの最新版をインストールできます。 + どちらのシステムを用いても、 + ローカルメディアやネットワーク上からソフトウェアをインストールできます。 この章を読むと、以下のことがわかります。 @@ -51,8 +52,8 @@ ソフトウェアのインストール - &unix; システムを使ったことのある人なら、 - サードパーティ製ソフトウェアの典型的なインストール手順が以下のようになることをご存知でしょう。 + &unix; システムでは、 + サードパーティ製ソフトウェアの典型的なインストール手順は以下のようになります。 @@ -67,9 +68,10 @@ - ドキュメント (INSTALL または + INSTALL または README ファイル、あるいは - doc/ サブディレクト中のファイル) を探しだし、 + doc/ + サブディレクトのファイルからドキュメントを探しだし、 ソフトウェアのインストール方法を調べる。 @@ -85,62 +87,39 @@ - すべてがうまくいったならば、インストール作業は以上です。 - もしインストールしているソフトウェアパッケージが、 - FreeBSD を意識して移植されたものでなければ、 + インストールしているソフトウェアパッケージが、 + &os; を意識して移植されたものでなければ、 適切に動くようコードを調べ、編集する必要があるかもしれません。 - あなたが望むのであれば、FreeBSD 上へのソフトウェアのインストールに - 従来 の方法を使い続けることができます。 - しかしながら、FreeBSD は - インストール時にかかるたくさんの労力を軽減する 2 つの技術、 - すなわち packages と ports を提供しています。 + &os; は、あなたのかわりにこれらのインストールの手順を実行してくれる + 2 つの技術を提供しています。 この文書を書いている時点では、&os.numports; - を越えるサードパーティ製アプリケーションがこれらの方法で利用可能となっています。 + を越えるサードパーティ製アプリケーションが利用可能です。 - FreeBSD package では、いかなるアプリケーションに対しても - ダウンロードする必要のあるファイルはただ一つです。 - package には、コンパイル済みのアプリケーションの全コマンド、 - 各種設定ファイルやドキュメントが含まれています。 - FreeBSD に用意されている + &os; の package は、コンパイル済みのアプリケーションの全コマンド、 + 各種設定ファイルやドキュメントを含んでいます。 + &os; に用意されている &man.pkg.add.1;, &man.pkg.delete.1;, &man.pkg.info.1; - といった package 管理コマンドで、 - ダウンロードした package ファイルを扱うことができます。 - 新しいアプリケーションをインストールするには、 - たった一つのコマンドを実行するだけです。 - - FreeBSD port は、 - アプリケーションをソースコードからコンパイルする際の処理を自動化するように設計されたファイルの集まりです。 - - プログラムをコンパイルする時のことを思い出して下さい。 - 通常、とてもたくさんの手順 - (ダウンロード、展開、パッチ作業、コンパイル、インストール) - を踏まなくてはなりません。 + といった package 管理コマンドで、package を扱うことができます。 + + &os; port は、 + アプリケーションをソースコードからコンパイルする際の処理を自動化するように設計されたファイルの集まりです。 port を構成するファイルは、 - これらすべての作業をあなたの代わりに行うために必要な情報を含んでいます。 - いくつかの簡単なコマンドを実行すると、 - 自動的にアプリケーションのソースコードがダウンロードされ、展開、 - パッチ作業、コンパイル、そして、インストール作業が行われます。 - - さらに ports システムは、pkg_add - コマンドや他の package 管理コマンドで扱うことのできる - packages を生成できます。 - これらのコマンドについては後の節で簡単に紹介します。 + 自動的にアプリケーションをダウンロードし、展開、パッチ作業、 + コンパイル、そしてインストールを行うために必要な情報を含んでいます。 + + さらに ports システムは、&os; の package + 管理コマンドで扱うことのできる packages を生成できます。 packages と ports は依存関係を理解します。 - ある特定のライブラリに依存する - アプリケーションをインストールするとします。 - また、アプリケーションとライブラリは FreeBSD ports や packages によって - 入手可能であるとします。 - アプリケーションを追加するために - pkg_add コマンドまたは ports システムを用いると、 - インストールされていないライブラリが検出され、 - 先に依存するライブラリが自動的にインストールされます。 - - 2 つの技術が非常に類似していて、 - なぜ FreeBSD がわざわざ両者を採用しているのか不思議に思うでしょう。 - packages と ports にはそれぞれ独自の特徴があり、 - どちらを使うかはあなたの好みによります。 + &man.pkg.add.1; または Ports Collection + を用いてアプリケーションをインストールすると、 + 依存するライブラリがまだインストールされていない場合には、 + 最初にライブラリが自動的にインストールされます。 + + 2 つの技術は非常に類似していますが、 + packages と ports にはそれぞれ独自の特徴があります。 + それぞれのアプリケーションのインストールに対する必要要件に応じてどちらかを選択してください。 package の利点 @@ -151,12 +130,11 @@ - packages はコンパイル作業を必要としません。 - このことは、Mozilla, + packages はコンパイルの時間を必要としません。 + このことは、遅いシステム上で Mozilla, KDE, または GNOME - といった大きなアプリケーションで重要となります。 - 特にシステムが遅い場合にはなおさら重要です。 + といった大きなアプリケーションを扱う場合に重要となります。 @@ -171,54 +149,44 @@ packages は、通常最も多くのシステムで実行できるように、 非常に保守的な設定で構築されています。 - port からインストールすることで、 - たとえば Pentium 4 や Athlon - プロセッサに特化したコードを生成するような + port からコンパイルすることで、 コンパイルオプションを指定できます。 - アプリケーションのなかには、コンパイル時に - プログラムの機能を決めるようなオプションを設定するものがあります。 + アプリケーションのなかには、 + どの機能をインストールするかをコンパイル時に設定するものがあります。 たとえば、Apache は多種多様な - ビルトインオプションを設定できます。 - port から構築することで、デフォルトオプションではなく、 - 自分でオプションを設定することができます。 + ビルトインオプションを設定できます。 設定を区別するために、同じアプリケーションに対して 複数の packages が存在することがあります。 たとえば、Ghostscript は - X11 サーバーがインストールされているかどうかにより、 + Xorg がインストールされているかどうかにより、 ghostscript package と ghostscript-nox11 package が選択可能となっています。 - packages でもこのような方法が可能ですが、 - アプリケーションのコンパイルオプションがさらに用意されている場合は困難となります。 + アプリケーションのコンパイルオプションが 1 つもしくは + 2 つ以上になると、 + 複数の packages を用意することは困難になります。 ライセンス条項で、 - バイナリでの配布を禁止しているソフトウェアがあります。 - それらはソースコードで配布されなくてはいけません。 + バイナリでの配布を禁止しているソフトウェアがあります。 + それらはソースコードで配布される必要があり、 + エンドユーザがコンパイルしなくてはなりません。 - バイナリ配布を信用していない人もいます。 - ソースコードがあれば、少なくともソースコードを読んで - (理論的には) 潜在的な問題点を自分で見つけ出すことができます。 + バイナリ配布を信用していない人や、 + 潜在的な問題点を見つけ出すためにソースコードを読むことを好む人がいます。 ローカルなパッチがある場合、 それを適用するためにソースコードが必要になります。 - - - ソースコードを手元に置いておきたい人たちもいます。 - 彼らは、退屈したときに眺めたり、あちこち解析してみたり、 - ソースコードを借用したり (もちろん、 - ライセンスが許せばの話ですが) するのです。 - ports の更新状況を把握するために、 @@ -228,51 +196,41 @@ アプリケーションをインストールする前に、 そのアプリケーションに関連したセキュリティ上の問題がないことを - で確認してください。 - - また、 - インストールされているアプリケーションに既知の脆弱性がないことを自動的に調べる - ports-mgmt/portaudit - をインストールしてもよいでしょう。 - このコマンドは、ビルド前の port についても調査します。 - インストールされている packages を確認する場合には、 - portaudit -F -a コマンドを使ってください。 + で確認するか、ports-mgmt/portaudit + をインストールしてください。インストールしたら、 + portaudit -F -a と入力して、 + インストールされているアプリケーションに既知の脆弱性がないことを確認してください。 - この章では、packages と ports を用いた FreeBSD 上での + この章では、packages と ports を用いた &os; 上での サードパーティ製ソフトウェアのインストール方法や管理方法について説明します。 - アプリケーションの探し方 - - どんなアプリケーションをインストールするにしても、 - まずあなたが何を望んで、 - またその名前がなんというのかを理解している必要があります。 + ソフトウェアの探し方 - FreeBSD 上で利用可能なアプリケーションのリストは常に増えています。 - 幸運にも、多くの方法で望むものを探すことができます。 + &os; 上で利用可能なアプリケーションのリストは常に増えています。 + インストールするソフトウェアを探す方法はたくさん用意されています。 - FreeBSD ウェブサイトは、 + &os; ウェブサイトは、 利用可能なすべてのアプリケーションの最新の一覧を、検索できる形で http://www.FreeBSD.org/ja/ports/ において公開しています。 - ports はカテゴリに分類されています。 - アプリケーションは、(名前を知っているならば) 名前で検索でき、 - あるカテゴリで利用可能なアプリケーションをすべて表示させることもできます。 + ports はアプリケーションの名前や、ソフトウェアのカテゴリで検索出来ます。 FreshPorts - Dan Langille は - - で FreshPorts を公開しています。 - FreshPorts は ports ツリー中のアプリケーションの変更を追跡します。 - 一つまたはそれ以上の ports を 監視 することができ、 - 変更があるとメールで更新情報を送ってくれます。 + Dan Langille は、包括的な検索ユーティリティや + Ports Collection にあるアプリケーションの変更点を追跡する + FreshPorts + を公開しています。 + 登録したユーザは、監視している ports がアップデートされた時に、 + そのことを自動的にメールで知らせてくれるような、 + カスタマイズ可能な監視リストを使うことができます。 @@ -282,30 +240,21 @@ Freecode () のようなサイトでアプリケーションを探して下さい。 その後、そのアプリケーションが ports で利用可能かどうかを - FreeBSD サイトで調べて下さい。 + &os; サイトで調べて下さい。 - port の正確な名前を知っていて、 - どのカテゴリに分類されているのかを知りたいだけなら、 + port がどのカテゴリに分類されているのかを知りたいのであれば、 &man.whereis.1; コマンドで調べることができます。 - 単に whereis file - と入力してください。file - の部分にはインストールしたいプログラム名を入れます。 - システム上でプログラムが見つかったら、 - そのプログラムのパスが次のように表示されます。 + whereis ファイル + と入力してください。ファイル + の部分にはインストールを考えているプログラム名を入れます。 &prompt.root; whereis lsof lsof: /usr/ports/sysutils/lsof - この表示は、lsof (システムユーティリティの一つ) が - /usr/ports/sysutils/lsof - というディレクトリにあることを示しています。 - - - - さらに、以下の例のように &man.echo.1; を使って - port が存在するかどうかを簡単に調べることもできます。 + さらに、以下の例のように &man.echo.1; + を使って調べることもできます。 &prompt.root; echo /usr/ports/*/*lsof* /usr/ports/sysutils/lsof @@ -317,15 +266,15 @@ lsof: /usr/ports/sysutils/lsof また、Ports Collection に備わっている検索機能を利用して port を検索する方法もあります。 - この検索機能を利用するには、カレントディレクトリが - /usr/ports である必要があります。 - そのディレクトリに移動したら、 - make search - name=プログラム名 + この検索機能を利用するには、 + cd コマンドを用いて + /usr/ports ディレクトリに移動し、make + search + name=ログラム名 と入力してください。 - プログラム名の部分には検索したいプログラム名を入れます。 - たとえば、lsof - を探したい場合には次のようにします。 + プログラム名 + の部分には検索したいソフトウェアの名前を入れてください。 + たとえば、lsof を探すには次のようにします。 &prompt.root; cd /usr/ports &prompt.root; make search name=lsof @@ -337,26 +286,18 @@ Index: sysutils B-deps: R-deps: - 出力のうち特に注意して見なければならないのは - Path: という行です。 - この行は port がどこにあるかを示しています。 - 出力される他の情報は port - をインストールする際には必要となるものではありませんので、 - ここでは触れないでおきます。 - - さらに、ports を検索するもう一つの機能があります。 - これは quicksearch と呼ばれる機能で、 - 出力される情報がより絞られます。 - この機能では search と同じパラメータを受け付けます。 - たとえば、lsof を検索すると以下のように出力されます。 + Path: という行は、 + port がどこにあるかを示しています。 + より絞られた情報を得るには、 + quicksearch と呼ばれる機能を使ってください。 + &prompt.root; cd /usr/ports &prompt.root; make quicksearch name=lsof Port: lsof-4.87.a,7 Path: /usr/ports/sysutils/lsof Info: Lists information about open files (similar to fstat(1)) - もっと詳しく検索するには、 make search key=string または @@ -365,12 +306,12 @@ Info: Lists information about open fil と入力してください。 string の部分には検索したいテキストを入れます。 - port 名、コメント、説明文および依存情報が検索されます。 - 探しているプログラムの名前を知らない場合でも、 - ある目的に関連した ports の検索に利用できます。 + プログラムの名前がわからない場合でも、 + ある目的に関連した ports の検索に利用できるよう、 + テキストの部分には、コメント、説明文および依存情報を入れることができます。 - どちらの場合 (search - および quicksearch) でも、 + search + および quicksearch を使う場合には、 検索文字列中の大文字と小文字を区別せずに検索が行われるので、 LSOF を検索した結果は、 lsof と同じ検索結果になります。 @@ -391,9 +332,9 @@ Info: Lists information about open fil - packages システムの利用 + バイナリ packages の利用 - FreeBSD には packages を管理するツールが複数あります。 + &os; には packages を管理するツールが複数あります。 sysinstall @@ -416,8 +357,7 @@ Info: Lists information about open fil pkg_add &man.pkg.add.1; は、ローカルファイルやネットワーク上のサーバから - FreeBSD ソフトウェア package を - インストールするためのユーティリティです。 + &os; バイナリ package をインストールするためのユーティリティです。 手動で package をダウンロードしてローカルからインストールする @@ -447,27 +387,22 @@ local: lsof-4.56.4.tgz remote: lsof-4.56 &prompt.root; pkg_add lsof-4.56.4.tgz - (FreeBSD CD-ROM セットのような) - ローカルな packages がない場合は、 - &man.pkg.add.1; に オプションをつける方が楽でしょう。 - このユーティリティは、このオプションを指定して実行すると + &os; CD-ROM セットのような、ローカルな packages がない場合は、 + &man.pkg.add.1; に オプションを付け加えてください。 + このオプションを指定して実行すると、 自動的に適切なオブジェクトの形式とリリースを判断し、 package を FTP サイトからダウンロードしてインストールします。 - + ユーザはこのほかに何もする必要はありません。 pkg_add &prompt.root; pkg_add -r lsof - 上の例では適当な package がダウンロードされた後、インストールされます。 - ユーザはこのほかに何もする必要はありません。 - メインの配布サイトではなく - &os; Package ミラーサイトの package を使うには、 - PACKAGESITE - 環境変数に利用したいサイトを設定してください。 + 別の &os; FTP ミラーサイトを使うには、 + PACKAGESITE 環境変数に利用したいサイトを設定してください。 &man.pkg.add.1; は、FTP_PASSIVE_MODE, FTP_PROXY, FTP_PASSWORD - といった環境変数を参照する &man.fetch.3; + といった環境変数を使う &man.fetch.3; を用いてファイルをダウンロードします。 ファイアウォールの内側であったり、 FTP/HTTP プロキシを使う場合には、 @@ -476,21 +411,20 @@ local: lsof-4.56.4.tgz remote: lsof-4.56 また、上の例で lsof-4.56.4 の代わりに lsof を使っていることに注意してください。 リモートフェッチ機能を使用する場合には、 - package のバージョン番号を取り除かなければなりません。 - &man.pkg.add.1; は自動的に最新版のアプリケーションを取得します。 + package のバージョン番号を取り除かなければなりません。 &os.current; または、&os.stable; を使用している場合、 - &man.pkg.add.1; は最新版のアプリケーションをダウンロードします。 + &man.pkg.add.1; は自動的に最新版のアプリケーションをダウンロードします。 -RELEASE を使用している場合には、 - そのバージョンのリリース時にビルドされた package がダウンロードされます。 + そのバージョンのリリース時にビルドされた package をダウンロードします。 この設定は PACKAGESITE を上書きすることで変更できます。 たとえば、&os; 8.1-RELEASE を使用している場合には、 &man.pkg.add.1; を実行するとデフォルトで ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.1-release/Latest/ から packages をダウンロードします。 - もし、&man.pkg.add.1; を使って - &os; 8-STABLE の packages をダウンロードしたければ、 + &man.pkg.add.1; を使って &os; 8-STABLE の packages + をダウンロードするには、 PACKAGESITE 環境変数を ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/Latest/ に設定してください。 @@ -500,15 +434,12 @@ local: lsof-4.56.4.tgz remote: lsof-4.56 という拡張子を持つファイルとして配布されており、 - や FreeBSD CD-ROM にあります。 - FreeBSD 4-CD セット (または PowerPak など) の CD はすべて、 - /packages ディレクトリに packages - があります。packages のレイアウトは、 + や &os; DVD の /packages ディレクトリにあります。 + packages のレイアウトは、 /usr/ports ツリーのものと同様です。 カテゴリごとにディレクトリがあり、 All ディレクトリにはすべての package - があります。 - + があります。 package システムのディレクトリ構造は ports のレイアウトと同一です。 両者が組み合わさって package/port システムが構成されます。 @@ -523,9 +454,9 @@ local: lsof-4.56.4.tgz remote: lsof-4.56 packages 管理 + &man.pkg.info.1; は、インストールされている - packages の一覧と説明を表示するユーティリティです。 - + packages の一覧と説明を表示します。 pkg_info @@ -535,11 +466,12 @@ local: lsof-4.56.4.tgz remote: lsof-4.56 colordiff-1.0.13 A tool to colorize diff output docbook-1.2 Meta-port for the different versions of the DocBook DTD ... + &man.pkg.version.1; は、インストールされている - packages のバージョンを要約して表示するユーティリティです。 - package のバージョンを、現在の ports ツリーのバージョンと - 比較します。 - + packages のバージョンを要約して表示します。 + また、package のバージョンを、 + 現在の ports ツリーのバージョンと比較します。 + pkg_version @@ -570,17 +502,17 @@ docbook = < インストールされているバージョンは、 - ローカル ports ツリーのものより古いです。 + ローカルにある ports ツリーのものより古いです。 >インストールされているバージョンは、 - ローカル ports ツリーのものより新しいです - (おそらくローカル ports ツリーは古くなっています)。 + ローカルにある ports ツリーのものより新しいです。 + すなわち、ローカルの ports ツリーはおそらく古くなっています。 ?インストールされた package を - ports インデックスの中に見つけることができません - (インストールされた port が Ports Collection から削除されたり、 - 名前が変更された場合などに起こります)。 + ports インデックスの中に見つけることができません。 + インストールされた port が Ports Collection から削除されたり、 + 名前が変更された場合などに起こります。 *複数のバージョンの package が存在します。 @@ -604,8 +536,9 @@ docbook = packages 削除 + インストールされている package を削除するには、 - &man.pkg.delete.1; ユーティリティを使ってください。 + &man.pkg.delete.1; を使ってください。 &prompt.root; pkg_delete xchat-1.7.1 @@ -614,9 +547,8 @@ docbook = すなわち、先ほどの例において xchat-1.7.1 を xchat とした場合には動作しません。 - インストールされている package のバージョンは、 - &man.pkg.version.1; を使うと簡単に調べることができます。 - バージョン番号のかわりにワイルドカードも使えます。 + &man.pkg.version.1; を使ってインストールされている package + のバージョンを調べるか、ワイルドカードを使ってください。 &prompt.root; pkg_delete xchat\* @@ -625,12 +557,10 @@ docbook = その他 - package に関するすべての情報は - /var/db/pkg ディレクトリ以下に置かれています。 - このディレクトリの下にあるファイルの中に、 - インストールされたファイルの一覧やインストールされた各 package - についての説明が含まれています。 - + + インストールされた各 package のファイルの一覧や説明といった、 + package に関するすべての情報は、 + /var/db/pkg ディレクトリ以下に置かれています。 @@ -639,8 +569,7 @@ docbook = package の管理 pkgng は、&os; における伝統的な - pkg_install package - 管理ツールの置き換えであり、バイナリ packages をより早く、 + package 管理ツールの置き換えであり、バイナリ packages をより早く、 より簡単に管理できるようにする数多くの機能を提供します。 pkgng の最初のリリースは 2012 年 8 月に行われました。 @@ -806,7 +735,7 @@ pkg-1.0.2 New generation package manag たとえば、 curl をインストールするには以下を実行してください。 - &prompt.root; pkg install curl + &prompt.root; pkg install curl Updating repository catalogue Repository catalogue is up-to-date, no need to fetch fresh copy The following packages will be installed: @@ -926,8 +855,7 @@ Deinstalling ca_root_nss-3.13.5... done< <application>pkgng</application> package データベースのバックアップ - pkg_install - package 管理システムとは異なり、 + 伝統的な package 管理システムとは異なり、 pkgng には package データベースをバックアップするメカニズムがあります。 package データベースの内容を手動でバックアップするには、 @@ -1047,7 +975,7 @@ Deinstalling ca_root_nss-3.13.5... done< Ports Collection の利用 このセクションでは、Ports Collection - を利用してシステムにプログラムをインストールしたり、 + を利用してプログラムをインストールしたり、 システムから削除したりする基本的な手順について説明します。 利用可能な make のターゲットや環境変数についての詳細は &man.ports.7; をご覧ください。 @@ -1071,7 +999,7 @@ Deinstalling ca_root_nss-3.13.5... done< Ports Collection とは、/usr/ports 以下に置かれる Makefile, 修正パッチ、 説明文などの一連のファイルのことです。このファイルのセットは、 - アプリケーションを構築して &os; にインストールするのに用いられます。 + アプリケーションをコンパイルして &os; にインストールするのに用いられます。 以下では、&os; のセットアップ時に Ports Collection をインストールしなかった場合に、 Ports Collection を準備する方法について示します。 @@ -1311,24 +1239,20 @@ Deinstalling ca_root_nss-3.13.5... done< ports インストール - 一番最初に知らなければならないのは、 - Ports Collection は スケルトン - と呼ばれるもので構成されているという事実です。 - port スケルトンは簡単に言うと、アプリケーションを FreeBSD - 上で正しくコンパイルしインストールする方法を提供する最小限のファイルのセットのことです。 - それぞれの port スケルトンには、次のファイルが含まれています。 - + + port スケルトンは、アプリケーションを &os; + 上で正しくコンパイルしインストールする方法を提供するファイルのセットのことです。 + それぞれの port スケルトンには、次のファイルが含まれています。 Makefile。 Makefile - にはアプリケーションのコンパイル方法やシステムのどこにインストールするかを指定する、 - さまざまな命令文が含まれています。 + にはアプリケーションのコンパイル方法やシステムのどこにインストールするかを指定する命令文が含まれています。 - distinfo ファイル。 + distinfo。 このファイルには、その port を構築するためにダウンロードする必要があるファイルのファイル名と、 それらのファイルがダウンロードによって壊れていないかを @@ -1337,30 +1261,20 @@ Deinstalling ca_root_nss-3.13.5... done< - files ディレクトリ。 - このディレクトリには FreeBSD - システム上でプログラムをコンパイルし、 + files。 + このディレクトリには &os; 上でプログラムをコンパイルし、 インストールするための修正パッチが含まれています。 - 修正パッチ (patch) とは基本的に、 - 個々のファイルに対する変更点を表した小さなファイル群のことです。 - ファイルはプレインテキスト形式で、 - 10 行目を削除 や - 26 行目を ... に変更 などと書かれています。 - 修正パッチは、diff (差分) とも呼ばれます。 - これは、修正パッチが &man.diff.1; - プログラムで作成されるからです。 - - このディレクトリには、その port の構築に必要な - その他のファイルが入る場合もあります。 + このディレクトリには、その port + の構築に必要なその他のファイルが入る場合もあります。 - pkg-descr ファイル。 - これにはプログラムの、複数行にわたる詳しい説明文が含まれます。 + pkg-descr。 + このファイルにはプログラムに関する、より詳しい説明文が含まれます。 - pkg-plist ファイル。 + pkg-plist。 これは、その port によってインストールされる全ファイルのリストです。 これにはプログラムを削除する際に、 どのファイルを削除すれば良いのかを ports @@ -1377,16 +1291,10 @@ Deinstalling ca_root_nss-3.13.5... done< url="&url.books.porters-handbook/index.html">port 作成者のためのハンドブック をご覧下さい。 - port はソースコードからアプリケーションを構築する方法を提供しますが、 - 実際のソースコードを含んではいません。 - ソースコードは CD-ROM やインターネットから入手できます。 - ソースコードはソフトウェア作者のお気に入りの形式で配布されます。 - たいてい、tar と gzip で作成された圧縮アーカイブとして配布されますが、 - 他のツールで圧縮されていたり、圧縮されずに配布されることもあります。 - どのような形式で配布されているかに関わらず、 - これらのプログラムのソースコードは distfile - と呼ばれています。 - 以下では &os; port をインストールする 2 つの方法について説明します。 + port は実際のソースコード (distfile とも呼ばれます) + を含んではいません。 + ソースコードはソフトウェアの作者が好む形式で配布されます。 + 以下では port をインストールする 2 つの方法について説明します。 ports をインストールするには、 @@ -1394,21 +1302,16 @@ Deinstalling ca_root_nss-3.13.5... done< - port をインストールする前に、 + port をコンパイルする前に、 Ports Collection が最新であることを確認してください。 - また、そのアプリケーションに関連したセキュリティ上の問題がないことを + また、その port に関連したセキュリティ上の問題がないことを - で確認してください。 - - - アプリケーションをインストールする前に、 - portaudit を使って - セキュリティに関する脆弱性を自動的に調べることができます。 - このツールは Ports Collection (ports-mgmt/portaudit) に用意されています。 + で確認してください。ports-mgmt/portaudit + をインストールしているのであれば、 新しく port をインストールする前に、 - portaudit -F コマンドを実行すると、 - 最新の脆弱性に関するデータベースがダウンロードされます。 + portaudit -F コマンドを実行して、 + 最新の脆弱性に関するデータベースをダウンロードしてください。 セキュリティの検査およびデータベースの更新は、 日々のセキュリティチェックで行なわれます。 詳しくは、&man.portaudit.1; および &man.periodic.8; @@ -1420,16 +1323,13 @@ Deinstalling ca_root_nss-3.13.5... done< /usr/ports/distfiles に手動で置いてください。 - まず、インストールしたい port のディレクトリに移動してください。 + まず、インストールしたい port のディレクトリに移動してください。 - &prompt.root; cd /usr/ports/sysutils/lsof + &prompt.root; cd /usr/ports/sysutils/lsof - lsof ディレクトリに移動すると、 - port スケルトンがあるのが確認できると思います。 - 次に行なうのは、port のコンパイルまたは - ビルド (build) です。 - これは、プロンプトから単に - make と入力するだけで行なえます。 + port をコンパイルまたは + ビルド (build) するには、プロンプトから + make と入力してください。 そうすると、次のような出力が現われるはずです。 &prompt.root; make @@ -1452,11 +1352,9 @@ Deinstalling ca_root_nss-3.13.5... done< ... &prompt.root; - コンパイルが終了してプロンプトに戻ることを確認してください。 - 次に port のインストールを行ないます。 - port をインストールするのに必要なのは、 - make コマンドに一つの単語、 - install を指定することだけです。 + コンパイルが終了すると、プロンプトに戻ります。 + 次に make install を使って、 + port のインストールを行ないます。 &prompt.root; make install ===> Installing for lsof-4.57 @@ -1474,14 +1372,13 @@ Deinstalling ca_root_nss-3.13.5... done< プロンプトに戻ったら、 インストールしたプログラムは実行できるようになっています。 lsof は高い権限で動作するプログラムなので、 - セキュリティに関する警告が表示されます。 - ports のコンパイルや - インストール中に表示されるこれらの警告に注意してください。 + セキュリティに関する警告が表示されます。ports + のコンパイルやインストール中に表示されるこれらの警告に注意してください。 コンパイル時に作成される作業用ディレクトリを削除すると良いでしょう。 このディレクトリにはコンパイル時に使用されるすべての一時ファイルが含まれています。 - このディレクトリを残しておくと、ディスク容量を消費するだけでなく、 - port を新しいバージョンへアップデートする際に問題を引き起こす可能性があります。 + このディレクトリを削除することで、ディスク容量を節約でき、また port + を新しいバージョンへアップデートする際に問題が起こる可能性を小さくします。 &prompt.root; make clean ===> Cleaning for lsof-4.57 @@ -1498,13 +1395,9 @@ Deinstalling ca_root_nss-3.13.5... done< デフォルトでは、ユーザに port のオプションを選択させる設定のため、 - 最初から make - install - を使って port をインストールすると、 - ユーザとの対話が起こり長時間待たされることがあります。 - 依存する port の数が多い場合には、一つの - port をインストールするだけでも大変面倒なことになる可能性があります。 - これを避けるには、まず最初に make + make install + だけの実行では、ユーザとの対話が起こり長時間待たされることがあります。 + 依存する port の数が多い場合に、これを避けるには、まず最初に make config-recursive を実行して設定を一括で行い、その後 make install @@ -1528,19 +1421,17 @@ Deinstalling ca_root_nss-3.13.5... done< シェルによってはコマンドの実行ファイルを探す時間を短縮するために、 環境変数 PATH に登録されている ディレクトリのコマンド一覧をキャッシュするものがあります。 - このようなシェルを使っているのであれば、 - port をインストールしたあとで、 - 新しくインストールされたコマンドを用いる前に、 - rehash コマンドを実行する必要があります。 - このコマンドは tcsh などのシェルで動作します。 - sh のようなシェルを使っているのであれば - hash -r を実行してください。 + tcsh を使っているのであれば、 + フルパスを指定することなく新しくインストールしたコマンドを利用できるように、 + rehash を実行してください。 + sh シェルを使っているのであれば + かわりに hash -r を実行してください。 詳細については、 あなたの使っているシェルのドキュメントをご覧ください。 - FreeBSD - Mall の FreeBSD Toolkit のようなサードパーティ製の DVD-ROM + &os; + Mall の &os; Toolkit のようなサードパーティ製の DVD-ROM 製品の中には distfiles を収録しているものがあります。 これらを Ports Collection で使うことができます。 DVD-ROM を /cdrom にマウントしてください。 @@ -1550,12 +1441,11 @@ Deinstalling ca_root_nss-3.13.5... done< 自動的に利用されます。 - port には CD-ROM - への収録を許可しないライセンス条項を持つものがあることに - 注意してください。 + port には DVD + への収録を許可しないライセンス条項を持つものがあります。 これにはダウンロード前に登録を必要としたり、 - 再配布が禁止されているなどという理由があります。 - CD-ROM に含まれていない port をインストールしたい場合には、 + 再配布が禁止されているという理由があります。 + DVD に含まれていない port をインストールしたい場合には、 ネットワークに接続する必要があります。 @@ -1572,21 +1462,19 @@ Deinstalling ca_root_nss-3.13.5... done< make fetch コマンドが用意されています。 (ネットワークに接続している時に) このコマンドを - ports のトップディレクトリ - (/usr/ports) で実行してください。 + /usr/ports で実行してください。 必要なファイルがダウンロードされます。 このコマンドは /usr/ports/net といった、より下の階層のカテゴリにおいても使うことができます。 ある port がライブラリやその他の ports に依存している場合には、 - それらの distfiles + 別のカテゴリの ports の distfiles はダウンロードされないことに注意してください。 - port が依存しているものもダウンロードしたければ - fetch の代わりに - fetch-recursive を使って下さい。 + port が依存しているすべてをダウンロードしたければ、 + makefetch-recursive + fetch を使ってください。 - 前述した make fetch - と同じように、トップディレクトリで make + トップディレクトリで make を実行するとすべての port がビルドされます。 しかしながら ports の中には同時に存在できないものがあったり、 異なる ports の別のファイルが同じ名前で @@ -1594,7 +1482,7 @@ Deinstalling ca_root_nss-3.13.5... done< めったにないことかもしれませんが、 - MASTER_SITES (ファイルをダウンロードしてくる場所) + デフォルトの MASTER_SITES に書かれているサイト以外から tarball を持ってくることが必要になる場合があります。 そのような場合には以下のように @@ -1609,8 +1497,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/ に変更しています。 - ports の中にはビルドオプションを指定できる - (または要求してくる) ものがあります。 + ports の中にはビルドオプションを指定できるものがあります。 このオプションを指定することで、 アプリケーションの機能の一部を有効もしくは無効にできます。 また、セキュリティオプションを設定したり、 @@ -1620,19 +1507,16 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/ security/gpgme や mail/sylpheed-claws などがあります。 - 利用可能なオプションがある場合にはメッセージが表示されます。 + 利用可能なオプションがある場合には、 + port をコンパイルする前にメニューが表示されます。 ports ディレクトリの変更 - 作業ディレクトリやターゲットディレクトリを - デフォルトのものから変更したほうが有用な場合 - (もしくは変更しなければならない場合) があります。 - WRKDIRPREFIX 変数と + WRKDIRPREFIX 変数と PREFIX 変数を変更することで、 - 違うディレクトリを使用することができます。 - たとえば、 + 作業ディレクトリやターゲットディレクトリをデフォルトのものから変更できます。 &prompt.root; make WRKDIRPREFIX=/usr/home/example/ports install @@ -1642,51 +1526,33 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/ &prompt.root; make PREFIX=/usr/home/example/local install - この場合、コンパイルは /usr/ports + この場合、port のコンパイルは /usr/ports でおこない、 /usr/home/example/local にインストールします。 - もちろん、 + そして、 &prompt.root; make WRKDIRPREFIX=../ports PREFIX=../local install - とすれば両者を組み合わせることが可能です - (省略せずに記述したらこのページに収めるには長すぎるのですが、 - 考え方は理解していただけたと思います)。 + とすれば両者を組み合わせることが可能です。 あるいは、これらを環境変数に設定する方法もあります。 - どのようにすれば良いかについては、 + どのように環境変数を設定するかについては、 あなたの使っているシェルのマニュアルページを参照してください。 - <command>imake</command> の使用 - - (X Window System に含まれる) imake を使用する - ports の場合は PREFIX が機能せず、 - /usr/X11R6 にインストールしようとします。 - また、Perl 関連の ports も同様に PREFIX を無視して - Perl ツリーにインストールします。 - これらの ports で PREFIX - がきちんと参照されるように変更するのは、ほとんど不可能です。 - - - - ports の再構築 - *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-all@FreeBSD.ORG Sat Feb 16 15:43:07 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3F99621D; Sat, 16 Feb 2013 15:43:07 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 1DD70F63; Sat, 16 Feb 2013 15:43:07 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1GFh71Q038813; Sat, 16 Feb 2013 15:43:07 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1GFh6ci038811; Sat, 16 Feb 2013 15:43:06 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201302161543.r1GFh6ci038811@svn.freebsd.org> From: Eitan Adler Date: Sat, 16 Feb 2013 15:43:06 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40979 - in head/en_US.ISO8859-1/books/handbook: . linuxemu X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Feb 2013 15:43:07 -0000 Author: eadler Date: Sat Feb 16 15:43:06 2013 New Revision: 40979 URL: http://svnweb.freebsd.org/changeset/doc/40979 Log: Corel no longer releases a version of WordPerfect for Linux. Netscape is no longer a useful browser. Approved by: bcr (mentor) Modified: head/en_US.ISO8859-1/books/handbook/book.xml head/en_US.ISO8859-1/books/handbook/linuxemu/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/book.xml Sat Feb 16 04:51:03 2013 (r40978) +++ head/en_US.ISO8859-1/books/handbook/book.xml Sat Feb 16 15:43:06 2013 (r40979) @@ -59,7 +59,6 @@ &tm-attrib.adaptec; &tm-attrib.adobe; &tm-attrib.apple; - &tm-attrib.corel; &tm-attrib.creative; &tm-attrib.cvsup; &tm-attrib.heidelberger; Modified: head/en_US.ISO8859-1/books/handbook/linuxemu/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/linuxemu/chapter.xml Sat Feb 16 04:51:03 2013 (r40978) +++ head/en_US.ISO8859-1/books/handbook/linuxemu/chapter.xml Sat Feb 16 15:43:06 2013 (r40979) @@ -59,11 +59,9 @@ run about 90% of all Linux applications without modification. This includes applications such as &staroffice;, the Linux version of - &netscape;, &adobe; &acrobat;, &realplayer;, &oracle;, - &wordperfect;, Doom, Quake, and more. It is also reported that in some situations, Linux binaries perform better on From owner-svn-doc-all@FreeBSD.ORG Sat Feb 16 15:43:09 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9B5F721E; Sat, 16 Feb 2013 15:43:09 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 83BF4F64; Sat, 16 Feb 2013 15:43:09 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1GFh9Kh038849; Sat, 16 Feb 2013 15:43:09 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1GFh9Ek038848; Sat, 16 Feb 2013 15:43:09 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201302161543.r1GFh9Ek038848@svn.freebsd.org> From: Eitan Adler Date: Sat, 16 Feb 2013 15:43:09 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40980 - head/en_US.ISO8859-1/books/handbook/printing X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Feb 2013 15:43:09 -0000 Author: eadler Date: Sat Feb 16 15:43:08 2013 New Revision: 40980 URL: http://svnweb.freebsd.org/changeset/doc/40980 Log: Twiddle with the poorly worded sentence. Discussed with: bjk Approved by: bcr (mentor) Modified: head/en_US.ISO8859-1/books/handbook/printing/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/printing/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/printing/chapter.xml Sat Feb 16 15:43:06 2013 (r40979) +++ head/en_US.ISO8859-1/books/handbook/printing/chapter.xml Sat Feb 16 15:43:08 2013 (r40980) @@ -178,11 +178,8 @@ Why You Should Use the Spooler - If you are the sole user of your system, you may be - wondering why you should bother with the spooler when you do - not need access control, header pages, or printer accounting. - While it is possible to enable direct access to a printer, - you should use the spooler anyway since: + The spooler still provides benefit on a single-user system + and should be used because: From owner-svn-doc-all@FreeBSD.ORG Sat Feb 16 15:43:11 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DB9CB21F; Sat, 16 Feb 2013 15:43:11 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id C3EC5F65; Sat, 16 Feb 2013 15:43:11 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1GFhBNI038890; Sat, 16 Feb 2013 15:43:11 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1GFhB0f038889; Sat, 16 Feb 2013 15:43:11 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201302161543.r1GFhB0f038889@svn.freebsd.org> From: Eitan Adler Date: Sat, 16 Feb 2013 15:43:11 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40981 - head/en_US.ISO8859-1/books/handbook/config X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Feb 2013 15:43:11 -0000 Author: eadler Date: Sat Feb 16 15:43:11 2013 New Revision: 40981 URL: http://svnweb.freebsd.org/changeset/doc/40981 Log: Fix FAQ id. Approved by: bcr (mentor) Modified: head/en_US.ISO8859-1/books/handbook/config/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/config/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/config/chapter.xml Sat Feb 16 15:43:08 2013 (r40980) +++ head/en_US.ISO8859-1/books/handbook/config/chapter.xml Sat Feb 16 15:43:11 2013 (r40981) @@ -607,7 +607,7 @@ HOME=/var/log editor: cron will notice that the file has changed and immediately begin using the updated version. See + url="&url.books.faq;/admin.html#root-not-found-cron-errors"> this FAQ entry for more information. From owner-svn-doc-all@FreeBSD.ORG Sat Feb 16 16:10:51 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 9C002E8; Sat, 16 Feb 2013 16:10:51 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 8E926140; Sat, 16 Feb 2013 16:10:51 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1GGApoU047102; Sat, 16 Feb 2013 16:10:51 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1GGAp9J047091; Sat, 16 Feb 2013 16:10:51 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201302161610.r1GGAp9J047091@svn.freebsd.org> From: Eitan Adler Date: Sat, 16 Feb 2013 16:10:51 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40982 - head/en_US.ISO8859-1/books/handbook/mirrors X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Feb 2013 16:10:51 -0000 Author: eadler Date: Sat Feb 16 16:10:50 2013 New Revision: 40982 URL: http://svnweb.freebsd.org/changeset/doc/40982 Log: Frys appears to no longer carry &os; Approved by: bcr (mentor) Modified: head/en_US.ISO8859-1/books/handbook/mirrors/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/mirrors/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/mirrors/chapter.xml Sat Feb 16 15:43:11 2013 (r40981) +++ head/en_US.ISO8859-1/books/handbook/mirrors/chapter.xml Sat Feb 16 16:10:50 2013 (r40982) @@ -12,24 +12,6 @@ CDROM and DVD Publishers - Retail Boxed Products - - &os; is available as a boxed product (&os; CDs, - additional software, and printed documentation) from several - retailers: - - - -
- Frys Electronics - WWW: -
- - - - - CD and DVD Sets &os; CD and DVD sets are available from many online From owner-svn-doc-all@FreeBSD.ORG Sat Feb 16 16:36:18 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 20F257CE; Sat, 16 Feb 2013 16:36:18 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 136A120E; Sat, 16 Feb 2013 16:36:18 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1GGaH6J055156; Sat, 16 Feb 2013 16:36:17 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1GGaHrA055155; Sat, 16 Feb 2013 16:36:17 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201302161636.r1GGaHrA055155@svn.freebsd.org> From: Eitan Adler Date: Sat, 16 Feb 2013 16:36:17 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40983 - head/en_US.ISO8859-1/books/faq X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Feb 2013 16:36:18 -0000 Author: eadler Date: Sat Feb 16 16:36:17 2013 New Revision: 40983 URL: http://svnweb.freebsd.org/changeset/doc/40983 Log: Reduce, but do not eliminate duplication of content (-E flag to igor). Approved by: bcr (mentor) Modified: head/en_US.ISO8859-1/books/faq/book.xml Modified: head/en_US.ISO8859-1/books/faq/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/faq/book.xml Sat Feb 16 16:10:50 2013 (r40982) +++ head/en_US.ISO8859-1/books/faq/book.xml Sat Feb 16 16:36:17 2013 (r40983) @@ -2964,8 +2964,8 @@ kern.timecounter.hardware: TSC -> i82 - You are not running &man.config.8; with the - option. + You are not running &man.config.8; with + . @@ -5425,9 +5425,8 @@ UserConfig> quit - 117 — Menu - key, to the left of the right-hand Ctrl - key + 117 — Menu, + to the left of the right-hand Ctrl @@ -5438,11 +5437,11 @@ UserConfig> quitTo have the Windows key-mappings enabled automatically every time you start X either put the - xmodmap commands in your - ~/.xinitrc file or, preferably, create - a file ~/.xmodmaprc and include the + xmodmap commands in + ~/.xinitrc or, preferably, create + a ~/.xmodmaprc and include the xmodmap options, one per line, then add - the following line to your + the following line to ~/.xinitrc: xmodmap $HOME/.xmodmaprc @@ -6442,8 +6441,8 @@ add 0 0 HISADDR RD light does not), the problem is with the remote end. If TD does not flash, the problem is local. With an internal modem, you will need - to use the set server command in your - ppp.conf file. When the hang occurs, + to use the set server command in + ppp.conf. When the hang occurs, connect to &man.ppp.8; using &man.pppctl.8;. If your network connection suddenly revives (PPP was revived due to the activity on the diagnostic socket) or if you cannot @@ -6544,9 +6543,8 @@ deny pred1 deflate deflate24 protocomp a use the bt or where commands to get a stack trace. Save the output of your gdb session, and - detach from the running process by the - quit command of - gdb. + detach from the running process by typing + quit. @@ -6775,8 +6773,8 @@ set dfilter 3 permit 0/0 0/0using email with a dialup connection in the &os; Handbook for details on how to create your own configuration file and what should go into it. You may also - want to add the following line to your - .mc file: + want to add the following line to + .mc: define(`confDELIVERY_MODE', `d')dnl @@ -6894,8 +6892,8 @@ ATDT1234567 Why does &man.ppp.8; get a Segmentation - fault, but I see no ppp.core - file? + fault, but I see no + ppp.core From owner-svn-doc-all@FreeBSD.ORG Sat Feb 16 16:36:20 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 8EDC37D1; Sat, 16 Feb 2013 16:36:20 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 691FD20F; Sat, 16 Feb 2013 16:36:20 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1GGaKEc055195; Sat, 16 Feb 2013 16:36:20 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1GGaK7K055194; Sat, 16 Feb 2013 16:36:20 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201302161636.r1GGaK7K055194@svn.freebsd.org> From: Eitan Adler Date: Sat, 16 Feb 2013 16:36:20 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40984 - head/en_US.ISO8859-1/books/developers-handbook/testing X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Feb 2013 16:36:20 -0000 Author: eadler Date: Sat Feb 16 16:36:19 2013 New Revision: 40984 URL: http://svnweb.freebsd.org/changeset/doc/40984 Log: Remove outdated comments. Discussed with: des Approved by: bcr (mentor) Modified: head/en_US.ISO8859-1/books/developers-handbook/testing/chapter.xml Modified: head/en_US.ISO8859-1/books/developers-handbook/testing/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/developers-handbook/testing/chapter.xml Sat Feb 16 16:36:17 2013 (r40983) +++ head/en_US.ISO8859-1/books/developers-handbook/testing/chapter.xml Sat Feb 16 16:36:19 2013 (r40984) @@ -430,15 +430,14 @@ HEAD for amd64, arm, i386, - i386/pc98, ia64, mips, powerpc, powerpc64, and sparc64, - which takes approximately four hours. + i386/pc98, ia64, mips, powerpc, powerpc64, and + sparc64. RELENG_9 and supported 9.X branches for amd64, arm, i386, i386/pc98, ia64, mips, powerpc, powerpc64, and - sparc64, which takes approximately three and a half - hours. + sparc64. @@ -449,8 +448,7 @@ RELENG_8 and supported 8.X branches for amd64, i386, - i386/pc98, ia64, mips, powerpc and sparc64, and each - branch takes approximately six hours. + i386/pc98, ia64, mips, powerpc and sparc64. @@ -461,8 +459,7 @@ RELENG_7 and supported 7.X branches for amd64, i386, - i386/pc98, ia64, powerpc, and sparc64, and each branch - takes approximately three hours. + i386/pc98, ia64, powerpc, and sparc64. @@ -485,13 +482,6 @@ Apache is set up to use index.cgi as DirectoryIndex. - - A Varnish - instance in front of Apache ensures that - index.cgi does not need to run more - than once every two minutes. - From owner-svn-doc-all@FreeBSD.ORG Sat Feb 16 16:36:23 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 11FAE7D2; Sat, 16 Feb 2013 16:36:23 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 0468D210; Sat, 16 Feb 2013 16:36:23 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1GGaMfe055231; Sat, 16 Feb 2013 16:36:22 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1GGaMOI055230; Sat, 16 Feb 2013 16:36:22 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201302161636.r1GGaMOI055230@svn.freebsd.org> From: Eitan Adler Date: Sat, 16 Feb 2013 16:36:22 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40985 - head/en_US.ISO8859-1/htdocs/projects X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Feb 2013 16:36:23 -0000 Author: eadler Date: Sat Feb 16 16:36:22 2013 New Revision: 40985 URL: http://svnweb.freebsd.org/changeset/doc/40985 Log: Remove ancient things. Approved by: bcr (mentor) Modified: head/en_US.ISO8859-1/htdocs/projects/newbies.xml Modified: head/en_US.ISO8859-1/htdocs/projects/newbies.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/projects/newbies.xml Sat Feb 16 16:36:19 2013 (r40984) +++ head/en_US.ISO8859-1/htdocs/projects/newbies.xml Sat Feb 16 16:36:22 2013 (r40985) @@ -78,13 +78,6 @@ ppp page for links to the other valuable information and the latest updates.

-

  • The - Complete &os; by Greg Lehey, published by O'Reilly. - This book assumes minimal UNIX experience and takes the - beginner step by step through each stage from installation to - everything you need to know to set up and run a &os; system. You - also get to understand what you are doing and why.

    • -

  • The &os; Handbook and Frequently Asked Questions (FAQ) are the main documents for &os;. Essential reading, they contain a lot of @@ -102,12 +95,6 @@ answers via the search page.

    • -

  • The main newsgroup for &os; is comp.unix.bsd.freebsd.misc. - You might want to keep an eye on comp.unix.bsd.freebsd.announce - as well.

    • -

  • Manual pages are good for reference but not always the best introduction for a novice. The more you work with man pages @@ -156,12 +143,6 @@ Pretty soon you will want to move on to a book that gives more coverage.

    • -

  • One book mentioned frequently by newbies is UNIX for - the Impatient by Paul W. Abrahams and Bruce R. Larson, published - by Addison-Wesley. It is intended both as a book for learning UNIX - and a reference, and includes an introduction to UNIX concepts and - handy chapter on using the X Window System.

    • -

  • Another popular book is UNIX Power Tools by Jerry Peek, Tim O'Reilly and Mike Loukides, published by O'Reilly and Associates. It is organized as a series of short articles each of @@ -189,25 +170,11 @@ HTML at a mirror site near you, or can be installed on your own system.

    • -

  • UNIX questions are dealt with in the newsgroup comp.unix.questions and the - associated - FAQ - from the RMIT FTP site. Newbies are likely to be most interested in - sections 1 and 2 initially.

    • - -

  • Another interesting newsgroup is comp.unix.user-friendly. - Although this newsgroup is for discussing user-friendliness, it can - contain some good information for newbies. The FAQ - is also available by FTP.

    • -

  • Many other web sites hold lists of UNIX tutorials and reference - material. One of the best places to start looking is the UNIX page - at Yahoo!.

    • - + material. One of the best places to start looking is the + little known search engine Google.

    +

    Learning about the X Window System

    @@ -220,13 +187,6 @@ more likely to be difficult for newcomers to digest.

      -

    • For basic information about installing, configuring and using the - X Window System, three of the books mentioned above have sections - dealing with X at beginner level: - The X Window System chapter - of the &os; Handbook, The Complete &os;, - and UNIX for the Impatient.

      • -

    • Before you can get X running exactly the way you like, you will need to choose a window manager. Visit the Window Managers for X From owner-svn-doc-all@FreeBSD.ORG Sat Feb 16 16:51:35 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C9061CB0; Sat, 16 Feb 2013 16:51:35 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id AFBD2291; Sat, 16 Feb 2013 16:51:35 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1GGpZBq060574; Sat, 16 Feb 2013 16:51:35 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1GGpZWS060573; Sat, 16 Feb 2013 16:51:35 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201302161651.r1GGpZWS060573@svn.freebsd.org> From: Eitan Adler Date: Sat, 16 Feb 2013 16:51:35 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40986 - head/en_US.ISO8859-1/books/fdp-primer X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Feb 2013 16:51:35 -0000 Author: eadler Date: Sat Feb 16 16:51:35 2013 New Revision: 40986 URL: http://svnweb.freebsd.org/changeset/doc/40986 Log: The FDP example is bad style... Approved by: bcr (mentor) Modified: head/en_US.ISO8859-1/books/fdp-primer/book.xml Modified: head/en_US.ISO8859-1/books/fdp-primer/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/fdp-primer/book.xml Sat Feb 16 16:36:22 2013 (r40985) +++ head/en_US.ISO8859-1/books/fdp-primer/book.xml Sat Feb 16 16:51:35 2013 (r40986) @@ -143,8 +143,7 @@ The names of files. - Edit your .login - file. + Edit .login. From owner-svn-doc-all@FreeBSD.ORG Sat Feb 16 16:51:38 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 0775FCB1; Sat, 16 Feb 2013 16:51:38 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id E4061292; Sat, 16 Feb 2013 16:51:37 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1GGpbOE060610; Sat, 16 Feb 2013 16:51:37 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1GGpbEi060609; Sat, 16 Feb 2013 16:51:37 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201302161651.r1GGpbEi060609@svn.freebsd.org> From: Eitan Adler Date: Sat, 16 Feb 2013 16:51:37 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40987 - head/en_US.ISO8859-1/books/arch-handbook X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Feb 2013 16:51:38 -0000 Author: eadler Date: Sat Feb 16 16:51:37 2013 New Revision: 40987 URL: http://svnweb.freebsd.org/changeset/doc/40987 Log: Add the years I made substantial changes to the arch handbook. Approved by: bcr (mentor) Modified: head/en_US.ISO8859-1/books/arch-handbook/book.xml Modified: head/en_US.ISO8859-1/books/arch-handbook/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/arch-handbook/book.xml Sat Feb 16 16:51:35 2013 (r40986) +++ head/en_US.ISO8859-1/books/arch-handbook/book.xml Sat Feb 16 16:51:37 2013 (r40987) @@ -31,6 +31,8 @@ 2004 2005 2006 + 2012 + 2013 The FreeBSD Documentation Project From owner-svn-doc-all@FreeBSD.ORG Sat Feb 16 17:47:02 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 232648A4; Sat, 16 Feb 2013 17:47:02 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 1120A6C5; Sat, 16 Feb 2013 17:47:02 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1GHl1aa076681; Sat, 16 Feb 2013 17:47:01 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1GHl1qk076679; Sat, 16 Feb 2013 17:47:01 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201302161747.r1GHl1qk076679@svn.freebsd.org> From: Eitan Adler Date: Sat, 16 Feb 2013 17:47:01 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40988 - in head/en_US.ISO8859-1/books/arch-handbook: driverbasics mac X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Feb 2013 17:47:02 -0000 Author: eadler Date: Sat Feb 16 17:47:00 2013 New Revision: 40988 URL: http://svnweb.freebsd.org/changeset/doc/40988 Log: All the bits about MAKEDEV and mknod should be removed. They haven't been necessary since 4.x. Noted by: jhb Approved by: bcr (mentor) Modified: head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml head/en_US.ISO8859-1/books/arch-handbook/mac/chapter.xml Modified: head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml Sat Feb 16 16:51:37 2013 (r40987) +++ head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml Sat Feb 16 17:47:00 2013 (r40988) @@ -43,7 +43,6 @@ linker facility `kld'. device nodes - MAKEDEV Most devices in a &unix;-like operating system are accessed through device-nodes, sometimes also called special files. @@ -155,46 +154,6 @@ KMOD=skeleton - - Accessing a Device Driver - - &unix; provides a common set of system calls for user - applications to use. The upper layers of the kernel dispatch - these calls to the corresponding device driver when a user - accesses a device node. The /dev/MAKEDEV - script makes most of the device nodes for your system but if you - are doing your own driver development it may be necessary to - create your own device nodes with - mknod. - - - Creating Static Device Nodes - - device nodesstatic - mknod - - The mknod command requires four - arguments to create a device node. You must specify the name - of the device node, the type of device, the major number of - the device, and the minor number of the device. - - - - Dynamic Device Nodes - - device nodesdynamic - devfs - - The device filesystem, or devfs, provides access to the - kernel's device namespace in the global filesystem namespace. - This eliminates the problems of potentially having a device - driver without a static device node, or a device node without - an installed device driver. Devfs is still a work in - progress, but it is already working quite nicely. - - - - Character Devices Modified: head/en_US.ISO8859-1/books/arch-handbook/mac/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/arch-handbook/mac/chapter.xml Sat Feb 16 16:51:37 2013 (r40987) +++ head/en_US.ISO8859-1/books/arch-handbook/mac/chapter.xml Sat Feb 16 17:47:00 2013 (r40988) @@ -5888,7 +5888,7 @@ Label destruction or EPERM for lack of privilege. This call may be made in a number of situations, including as a result of calls to &man.open.2; with - O_CREAT, &man.mknod.2;, &man.mkfifo.2;, and + O_CREAT, &man.mkfifo.2;, and others. From owner-svn-doc-all@FreeBSD.ORG Sat Feb 16 23:32:15 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B00EB48E; Sat, 16 Feb 2013 23:32:15 +0000 (UTC) (envelope-from pawel@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 9D865FCE; Sat, 16 Feb 2013 23:32:15 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1GNWFmJ082732; Sat, 16 Feb 2013 23:32:15 GMT (envelope-from pawel@svn.freebsd.org) Received: (from pawel@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1GNWFtX082731; Sat, 16 Feb 2013 23:32:15 GMT (envelope-from pawel@svn.freebsd.org) Message-Id: <201302162332.r1GNWFtX082731@svn.freebsd.org> From: Pawel Pekala Date: Sat, 16 Feb 2013 23:32:15 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40989 - head/en_US.ISO8859-1/articles/contributors X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Feb 2013 23:32:15 -0000 Author: pawel (ports committer) Date: Sat Feb 16 23:32:15 2013 New Revision: 40989 URL: http://svnweb.freebsd.org/changeset/doc/40989 Log: For print/qpdf PR: ports/174982 Modified: head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Modified: head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml ============================================================================== --- head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Sat Feb 16 17:47:00 2013 (r40988) +++ head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Sat Feb 16 23:32:15 2013 (r40989) @@ -2603,6 +2603,11 @@ + Dmitry Kazarov + d.y.kazarov@mail.ru + + + Dmitry Khrustalev dima@xyzzy.machaon.ru