From owner-svn-doc-head@FreeBSD.ORG Sun Feb 3 00:59:16 2013 Return-Path: Delivered-To: svn-doc-head@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 3B0075AC; Sun, 3 Feb 2013 00:59:16 +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 17FB5DAF; Sun, 3 Feb 2013 00:59:16 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r130xFh2067105; Sun, 3 Feb 2013 00:59:15 GMT (envelope-from ryusuke@svn.freebsd.org) Received: (from ryusuke@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r130xFYI067104; Sun, 3 Feb 2013 00:59:15 GMT (envelope-from ryusuke@svn.freebsd.org) Message-Id: <201302030059.r130xFYI067104@svn.freebsd.org> From: Ryusuke SUZUKI Date: Sun, 3 Feb 2013 00:59:15 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40875 - head/ja_JP.eucJP/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-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Feb 2013 00:59:16 -0000 Author: ryusuke Date: Sun Feb 3 00:59:15 2013 New Revision: 40875 URL: http://svnweb.freebsd.org/changeset/doc/40875 Log: - Merge the following from the English version: r40824 -> r40874 head/ja_JP.eucJP/books/handbook/mirrors/chapter.xml Modified: head/ja_JP.eucJP/books/handbook/mirrors/chapter.xml Modified: head/ja_JP.eucJP/books/handbook/mirrors/chapter.xml ============================================================================== --- head/ja_JP.eucJP/books/handbook/mirrors/chapter.xml Sat Feb 2 23:22:37 2013 (r40874) +++ head/ja_JP.eucJP/books/handbook/mirrors/chapter.xml Sun Feb 3 00:59:15 2013 (r40875) @@ -3,7 +3,7 @@ The FreeBSD Documentation Project The FreeBSD Japanese Documentation Project - Original revision: r40824 + Original revision: r40874 $FreeBSD$ --> @@ -666,7 +666,7 @@ °Ê²¼¤ÎÎã¤Ç¤Ï¡¢Ports Collection ¤ò western US ¥ê¥Ý¥¸¥È¥ê¤«¤é - HTTPS ¥×¥í¥È¥³¥ë¤ò»È¤Ã¤Æ¡¢¥Á¥§¥Ã¥¯¥¢¥¦¥È¤·¤Þ¤¹¡£ + HTTPS ¥×¥í¥È¥³¥ë¤ò»È¤Ã¤Æ¡¢¥Á¥§¥Ã¥¯¥¢¥¦¥È¤·¤Þ¤¹¡£ ¤½¤·¤Æ¤½¤ì¤é¤Ï¡¢ /usr/ports ¤Î¥í¡¼¥«¥ëºî¶È¥³¥Ô¡¼¤ËÃÖ¤«¤ì¤Þ¤¹¡£ @@ -674,7 +674,7 @@ ¤½¤ì¤¬ svn ¤Ë¤è¤Ã¤ÆÀ¸À®¤µ¤ì¤¿¤â¤Î¤Ç¤Ê¤±¤ì¤Ð¡¢ ¥Á¥§¥Ã¥¯¥¢¥¦¥È¤¹¤ëÁ°¤Ë¡¢Ì¾Á°¤òÊѹ¹¤¹¤ë¤«ºï½ü¤·¤Æ¤¯¤À¤µ¤¤¡£ - &prompt.root; svn checkout https://svn0.us-west.FreeBSD.org/ports/head /usr/ports + &prompt.root; svn checkout https://svn0.us-west.FreeBSD.org/ports/head /usr/ports ½é¤á¤Æ¥Á¥§¥Ã¥¯¥¢¥¦¥È¤¹¤ëºÝ¤Ë¤Ï¡¢ ¥ê¥â¡¼¥È¥ê¥Ý¥¸¥È¥ê¤Î¤¹¤Ù¤Æ¤Î¥Ö¥é¥ó¥Á¤ò¥À¥¦¥ó¥í¡¼¥É¤¹¤ë¤Î¤Ç»þ´Ö¤¬¤«¤«¤ê¤Þ¤¹¡£ @@ -722,7 +722,7 @@ - <application>Subversion</application> ¥µ¥¤¥È + <application>Subversion</application> ¥ß¥é¡¼¥µ¥¤¥È Subversion Repository @@ -798,6 +798,39 @@ + + HTTPS ¤Ï¿ä¾©¤µ¤ì¤Æ¤¤¤ë¥×¥í¥È¥³¥ë¤Ç¤¹¡£ + ¾¤Î¥³¥ó¥Ô¥å¡¼¥¿¤¬ &os; ¥ß¥é¡¼¤òÁõ¤¦ (°ìÈÌŪ¤Ë¤Ï + ¥Þ¥ó¡¦¥¤¥ó¡¦¥¶¡¦¥ß¥É¥ë ¹¶·â¤È¤·¤ÆÃΤé¤ì¤Æ¤¤¤Þ¤¹) ¤³¤È¤ä¡¢ + ¤â¤·¤¯¤Ï¡¢¥¨¥ó¥É¥æ¡¼¥¶¤ËÂФ·¹¥¤Þ¤·¤¯¤Ê¤¤ÆâÍƤòÁ÷¤ê¤Ä¤±¤è¤¦¤È¤¤¤¦¤³¤È¤ËÂФ·Êݸî¤ò¹Ô¤¤¤Þ¤¹¡£ + + HTTPS ¥ß¥é¡¼¤Ø¤ÎºÇ½é¤ÎÀܳ¤ÎºÝ¤Ë¤Ï¡¢ + ¥µ¡¼¥Ð¤Î ¥Õ¥£¥ó¥¬¡¼¥×¥ê¥ó¥È ¤Î³Îǧ¤òµá¤á¤é¤ì¤Þ¤¹¡£ + + Error validating server certificate for 'https://svn0.us-west.freebsd.org:443': + - The certificate is not issued by a trusted authority. Use the + fingerprint to validate the certificate manually! +Certificate information: + - Hostname: svnmir.ysv.FreeBSD.org + - Valid: from Fri, 24 Aug 2012 22:04:04 GMT until Sat, 24 Aug 2013 22:04:04 GMT + - Issuer: clusteradm, FreeBSD.org, CA, US + - Fingerprint: 79:35:8f:ca:6d:34:d9:30:44:d1:00:af:33:4d:e6:11:44:4d:15:ec +(R)eject, accept (t)emporarily or accept (p)ermanently? + + ¥Õ¥£¥ó¥¬¡¼¥×¥ê¥ó¥È¤ò¾å¤Îɽ¤Î°ìÍ÷¤Î¤â¤Î¤È¾È¹ç¤·¤Æ¤¯¤À¤µ¤¤¡£ + ¥Õ¥£¥ó¥¬¡¼¥×¥ê¥ó¥È¤¬°ìÃפ·¤¿¤é¡¢ + ¥µ¡¼¥Ð¤Î¥»¥­¥å¥ê¥Æ¥£¾ÚÌÀ½ñ¤ò°ì»þŪ (permanently) + ¤â¤·¤¯¤Ï¹±µ×Ū (temporarily) ¤Ë¼õ¤±Æþ¤ì¤Æ¤¯¤À¤µ¤¤¡£ + °ì»þŪ¤Êǧ¾Ú¤Ç¤¢¤ì¤Ð¡¢¥µ¡¼¥Ð¤È¤Î°ì²ó¤Î¥»¥Ã¥·¥ç¥ó¤ÇÍ­¸ú´ü¸Â¤¬ÀÚ¤ì¤ë¤¿¤á¡¢ + ¼¡²ó¤ÎÀܳ»þ¤Ë¤Ï¤â¤¦°ìÅÙ¸¡¾Ú¤¬¹Ô¤ï¤ì¤Þ¤¹¡£ + ¹±¾ïŪ¤Êǧ¾Ú¤òÁª¤ó¤À¾ì¹ç¤Ë¤Ï¡¢Ç§¾Ú¤Î¤¿¤á¤Î¾ÚÌÀ½ñ¤¬ + ~/.subversion/auth/ ¤ËÊݸ¤µ¤ì¡¢ + Í­¸ú´ü¸Â¤¬ÀÚ¤ì¤ë¤Þ¤Ç¤Ï¡¢¥Õ¥£¥ó¥¬¡¼¥×¥ê¥ó¥È¤Î³Îǧ¤Ïµá¤á¤é¤ì¤Þ¤»¤ó¡£ + + ¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤Þ¤¿¤Ï¾¤ÎÌäÂê¤Î¤¿¤á¡¢HTTPS + ¤ò»È¤¨¤Ê¤±¤ì¤Ð¡¢Å¾Á÷®ÅÙ¤¬¤è¤ê¾¯¤·Áᤤ SVN ¤ò»È¤Ã¤Æ¤¯¤À¤µ¤¤¡£ + ξÊý¤ò»È¤¨¤Ê¤¤¾ì¹ç¤Ë¤Ï¡¢ + HTTP ¤ò»È¤Ã¤Æ¤¯¤À¤µ¤¤¡£ From owner-svn-doc-head@FreeBSD.ORG Sun Feb 3 17:38:17 2013 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A4B0E42B; Sun, 3 Feb 2013 17:38:17 +0000 (UTC) (envelope-from issyl0@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 971A1280; Sun, 3 Feb 2013 17:38: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 r13HcHQ2067450; Sun, 3 Feb 2013 17:38:17 GMT (envelope-from issyl0@svn.freebsd.org) Received: (from issyl0@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r13HcH9m067449; Sun, 3 Feb 2013 17:38:17 GMT (envelope-from issyl0@svn.freebsd.org) Message-Id: <201302031738.r13HcH9m067449@svn.freebsd.org> From: Isabell Long Date: Sun, 3 Feb 2013 17:38:17 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40876 - head/en_US.ISO8859-1/books/handbook/dtrace X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Feb 2013 17:38:17 -0000 Author: issyl0 Date: Sun Feb 3 17:38:17 2013 New Revision: 40876 URL: http://svnweb.freebsd.org/changeset/doc/40876 Log: Fix a dead sun.com link by changing it to oracle.com. PR: docs/175788 Approved by: gabor (mentor) Modified: head/en_US.ISO8859-1/books/handbook/dtrace/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/dtrace/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/dtrace/chapter.xml Sun Feb 3 00:59:15 2013 (r40875) +++ head/en_US.ISO8859-1/books/handbook/dtrace/chapter.xml Sun Feb 3 17:38:17 2013 (r40876) @@ -388,7 +388,7 @@ Elapsed Times for processes csh, to C++. An in depth discussion of the language is beyond the scope of this document. It is extensively discussed at . + url="http://wikis.oracle.com/display/DTrace/Documentation">. From owner-svn-doc-head@FreeBSD.ORG Mon Feb 4 00:21:19 2013 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C0A572EA; Mon, 4 Feb 2013 00:21:19 +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 A925CE5; Mon, 4 Feb 2013 00:21: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 r140LJNG003161; Mon, 4 Feb 2013 00:21:19 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r140LJtk003159; Mon, 4 Feb 2013 00:21:19 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201302040021.r140LJtk003159@svn.freebsd.org> From: Eitan Adler Date: Mon, 4 Feb 2013 00:21:19 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40879 - 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-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 00:21:19 -0000 Author: eadler Date: Mon Feb 4 00:21:19 2013 New Revision: 40879 URL: http://svnweb.freebsd.org/changeset/doc/40879 Log: Pointing users to the release is a non-answer of which the FAQ offers no additional value. As such, remove the question. Approved by: bcr (mentor, implicit) 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 Sun Feb 3 21:28:23 2013 (r40878) +++ head/en_US.ISO8859-1/books/faq/book.xml Mon Feb 4 00:21:19 2013 (r40879) @@ -2035,17 +2035,6 @@ bindkey ^[[3~ delete-char # for xterm

- - Which network cards does &os; support? - - - - See the Hardware Notes supplied with each release of - &os; for a more complete list. - - - - Is there a native driver for the Broadcom 43xx cards? From owner-svn-doc-head@FreeBSD.ORG Mon Feb 4 00:21:25 2013 Return-Path: Delivered-To: svn-doc-head@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 CDA8C322; Mon, 4 Feb 2013 00:21:25 +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 C0AD6E7; Mon, 4 Feb 2013 00:21: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 r140LPnG003208; Mon, 4 Feb 2013 00:21:25 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r140LPQL003207; Mon, 4 Feb 2013 00:21:25 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201302040021.r140LPQL003207@svn.freebsd.org> From: Eitan Adler Date: Mon, 4 Feb 2013 00:21:25 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40880 - 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-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 00:21:25 -0000 Author: eadler Date: Mon Feb 4 00:21:25 2013 New Revision: 40880 URL: http://svnweb.freebsd.org/changeset/doc/40880 Log: The answer is wrong, and the correct one involves pointing poeple to the release notea and man page which is a non-answer. Remoeve the question. Discussed on: -multimedia Approved by: bcr (mentor, implicit) 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 Mon Feb 4 00:21:19 2013 (r40879) +++ head/en_US.ISO8859-1/books/faq/book.xml Mon Feb 4 00:21:25 2013 (r40880) @@ -61,7 +61,6 @@ &tm-attrib.freebsd; &tm-attrib.adobe; - &tm-attrib.creative; &tm-attrib.ibm; &tm-attrib.ieee; &tm-attrib.intel; @@ -2053,30 +2052,6 @@ bindkey ^[[3~ delete-char # for xterm

- - Which sound cards are supported by &os;? - - - - &os; supports various sound cards (for more details, - see &os; Release Information - and the &man.snd.4; manual page). There is also limited - support for MPU-401 and compatible MIDI cards. Cards - conforming to the µsoft; Sound System specification - are also supported. - - - This is only for sound! This driver does not - support CD-ROMs, SCSI or joysticks on these cards, except - for the &soundblaster;. The &soundblaster; SCSI - interface and some non-SCSI CD-ROMs are supported, but - you cannot boot off this device. - - - - - Workarounds for no sound from my &man.pcm.4; sound card? From owner-svn-doc-head@FreeBSD.ORG Mon Feb 4 13:29:41 2013 Return-Path: Delivered-To: svn-doc-head@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 B3F44433; Mon, 4 Feb 2013 13:29:41 +0000 (UTC) (envelope-from gahr@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 9C2941BEA; Mon, 4 Feb 2013 13:29: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 r14DTfPD045146; Mon, 4 Feb 2013 13:29:41 GMT (envelope-from gahr@svn.freebsd.org) Received: (from gahr@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r14DTfYi045145; Mon, 4 Feb 2013 13:29:41 GMT (envelope-from gahr@svn.freebsd.org) Message-Id: <201302041329.r14DTfYi045145@svn.freebsd.org> From: Pietro Cerutti Date: Mon, 4 Feb 2013 13:29:41 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40884 - head/en_US.ISO8859-1/htdocs/donations X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 13:29:41 -0000 Author: gahr (ports committer) Date: Mon Feb 4 13:29:41 2013 New Revision: 40884 URL: http://svnweb.freebsd.org/changeset/doc/40884 Log: - Document Marco Dola's donation of 2x Kingston KVR1333D3N9/2G RAM banks to gavin@. Modified: head/en_US.ISO8859-1/htdocs/donations/donors.xml (contents, props changed) Modified: head/en_US.ISO8859-1/htdocs/donations/donors.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/donations/donors.xml Mon Feb 4 10:45:52 2013 (r40883) +++ head/en_US.ISO8859-1/htdocs/donations/donors.xml Mon Feb 4 13:29:41 2013 (r40884) @@ -2919,6 +2919,13 @@ garga received + + + Marco Dola + 2x Kingston KVR1333D3N9/2G RAM banks + gavin + received + From owner-svn-doc-head@FreeBSD.ORG Mon Feb 4 17:28:15 2013 Return-Path: Delivered-To: svn-doc-head@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 1C467D90; Mon, 4 Feb 2013 17:28:15 +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 09E4AD03; Mon, 4 Feb 2013 17:28: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 r14HSExE020786; Mon, 4 Feb 2013 17:28:14 GMT (envelope-from rene@svn.freebsd.org) Received: (from rene@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r14HSEqj020785; Mon, 4 Feb 2013 17:28:14 GMT (envelope-from rene@svn.freebsd.org) Message-Id: <201302041728.r14HSEqj020785@svn.freebsd.org> From: Rene Ladan Date: Mon, 4 Feb 2013 17:28:14 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40885 - head/nl_NL.ISO8859-1/articles/contributing X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 17:28:15 -0000 Author: rene Date: Mon Feb 4 17:28:14 2013 New Revision: 40885 URL: http://svnweb.freebsd.org/changeset/doc/40885 Log: MFen r40061 -> r40773 Modified: head/nl_NL.ISO8859-1/articles/contributing/article.xml Modified: head/nl_NL.ISO8859-1/articles/contributing/article.xml ============================================================================== --- head/nl_NL.ISO8859-1/articles/contributing/article.xml Mon Feb 4 13:29:41 2013 (r40884) +++ head/nl_NL.ISO8859-1/articles/contributing/article.xml Mon Feb 4 17:28:14 2013 (r40885) @@ -10,7 +10,7 @@ $FreeBSD$ %SOURCE% en_US.ISO8859-1/articles/contributing/article.xml - %SRCID% 40061 + %SRCID% 40773 -->
@@ -534,7 +534,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE PO De &os; Foundation is een non-profit, belastinguitgesloten stichting die opgericht is om de doelen van het &os; Project verder te verspreiden. Als een 501(c)3-entiteit is de - Foundation over het algemeen uitgesloten van van + Foundation over het algemeen uitgesloten van inkomstenbelasting van de overheid van de Verenigde Staten alsook van inkomstenbelasting van de staat Colorado. Donaties aan een entiteit die van belasting is uitgesloten zijn vaak aftrekbaar @@ -543,8 +543,9 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE PO Donaties kunnen als check verstuurd worden aan:
The FreeBSD Foundation - 7321 Brockway Dr. - Boulder, CO 80303 + P.O. Box 20247 + Boulder, + CO 80308 USA
From owner-svn-doc-head@FreeBSD.ORG Mon Feb 4 17:32:20 2013 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 88C9379; Mon, 4 Feb 2013 17:32: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 6BB2FD79; Mon, 4 Feb 2013 17:32: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 r14HWKja023043; Mon, 4 Feb 2013 17:32:20 GMT (envelope-from rene@svn.freebsd.org) Received: (from rene@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r14HWIHg023025; Mon, 4 Feb 2013 17:32:18 GMT (envelope-from rene@svn.freebsd.org) Message-Id: <201302041732.r14HWIHg023025@svn.freebsd.org> From: Rene Ladan Date: Mon, 4 Feb 2013 17:32:18 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40886 - in head/nl_NL.ISO8859-1/books/handbook: audit disks filesystems firewalls jails linuxemu mail multimedia network-servers ppp-and-slip security virtualization X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 17:32:20 -0000 Author: rene Date: Mon Feb 4 17:32:17 2013 New Revision: 40886 URL: http://svnweb.freebsd.org/changeset/doc/40886 Log: MFen the Dutch Handbook: - audit r39825 -> r40792 - disks r40676 -> r40792 - filesystems r40681 -> r40792 - firewalls r40732 -> r40792 (while here remove some spurious text) - jails r39631 -> r40792 - linuxemu r40735 -> 40792 - mail r40216 -> 40792 - multimedia r40784 -> r40792 - network-servers r40744 -> r40792 - ppp-and-slip r40778 -> r40792 - security r40749 -> r40792 - virtualization r40780 -> r40792 Some igor fixes while here. Modified: head/nl_NL.ISO8859-1/books/handbook/audit/chapter.xml head/nl_NL.ISO8859-1/books/handbook/disks/chapter.xml head/nl_NL.ISO8859-1/books/handbook/filesystems/chapter.xml head/nl_NL.ISO8859-1/books/handbook/firewalls/chapter.xml head/nl_NL.ISO8859-1/books/handbook/jails/chapter.xml head/nl_NL.ISO8859-1/books/handbook/linuxemu/chapter.xml head/nl_NL.ISO8859-1/books/handbook/mail/chapter.xml head/nl_NL.ISO8859-1/books/handbook/multimedia/chapter.xml head/nl_NL.ISO8859-1/books/handbook/network-servers/chapter.xml head/nl_NL.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml head/nl_NL.ISO8859-1/books/handbook/security/chapter.xml head/nl_NL.ISO8859-1/books/handbook/virtualization/chapter.xml Modified: head/nl_NL.ISO8859-1/books/handbook/audit/chapter.xml ============================================================================== --- head/nl_NL.ISO8859-1/books/handbook/audit/chapter.xml Mon Feb 4 17:28:14 2013 (r40885) +++ head/nl_NL.ISO8859-1/books/handbook/audit/chapter.xml Mon Feb 4 17:32:17 2013 (r40886) @@ -4,7 +4,7 @@ $FreeBSD$ %SOURCE% en_US.ISO8859-1/books/handbook/audit/chapter.xml - %SRCID% 39825 + %SRCID% 40792 --> herstart van het systeem of door het handmatig starten van de audit daemon: - /etc/rc.d/auditd start + service auditd start Modified: head/nl_NL.ISO8859-1/books/handbook/disks/chapter.xml ============================================================================== --- head/nl_NL.ISO8859-1/books/handbook/disks/chapter.xml Mon Feb 4 17:28:14 2013 (r40885) +++ head/nl_NL.ISO8859-1/books/handbook/disks/chapter.xml Mon Feb 4 17:32:17 2013 (r40886) @@ -5,7 +5,7 @@ $FreeBSD$ %SOURCE% en_US.ISO8859-1/books/handbook/disks/chapter.xml - %SRCID% 40676 + %SRCID% 40792 --> @@ -3603,7 +3603,7 @@ Filesystem 1K-blocks Used Avail Capacity Vervolgens dient inetd opnieuw gestart te worden: - &prompt.root; /etc/rc.d/inetd restart + &prompt.root; service inetd restart @@ -4693,7 +4693,7 @@ Device 1K-blocks Used Av starten: &prompt.root; hastctl create test -&prompt.root; /etc/rc.d/hastd onestart +&prompt.root; service hastd onestart Het is niet mogelijk om GEOM-aanbieders met @@ -4824,7 +4824,7 @@ notify 30 { Herstart &man.devd.8; op beide knooppunten om de nieuwe configuratie te laten gelden: - &prompt.root; /etc/rc.d/devd restart + &prompt.root; service devd restart Als het interface carp0 aan of uit gaat (i.e., de toestand van het interface verandert), genereert het systeem Modified: head/nl_NL.ISO8859-1/books/handbook/filesystems/chapter.xml ============================================================================== --- head/nl_NL.ISO8859-1/books/handbook/filesystems/chapter.xml Mon Feb 4 17:28:14 2013 (r40885) +++ head/nl_NL.ISO8859-1/books/handbook/filesystems/chapter.xml Mon Feb 4 17:32:17 2013 (r40886) @@ -4,7 +4,7 @@ $FreeBSD$ %SOURCE% en_US.ISO8859-1/books/handbook/filesystems/chapter.xml - %SRCID% 40681 + %SRCID% 40792 --> @@ -218,7 +218,7 @@ vfs.zfs.vdev.cache.size="5M" &prompt.root; echo 'zfs_enable="YES"' >> /etc/rc.conf -&prompt.root; /etc/rc.d/zfs start +&prompt.root; service zfs start In het resterende deel van dit document wordt aangenomen dat er drie SCSI-schijven beschikbaar zijn, Modified: head/nl_NL.ISO8859-1/books/handbook/firewalls/chapter.xml ============================================================================== --- head/nl_NL.ISO8859-1/books/handbook/firewalls/chapter.xml Mon Feb 4 17:28:14 2013 (r40885) +++ head/nl_NL.ISO8859-1/books/handbook/firewalls/chapter.xml Mon Feb 4 17:32:17 2013 (r40886) @@ -5,7 +5,7 @@ $FreeBSD$ %SOURCE% en_US.ISO8859-1/books/handbook/firewalls/chapter.xml - %SRCID% 40732 + %SRCID% 40792 --> @@ -262,7 +262,7 @@ Draai vervolgens het opstartscript om de module te laden: - &prompt.root; /etc/rc.d/pf start + &prompt.root; service pf start Merk op dat de PF module niet laadt als het het instellingenbestand met de regelverzameling niet kan vinden. De standaardlocatie is @@ -290,7 +290,7 @@ Draai vervolgens het opstartscript om de module te laden: - &prompt.root; /etc/rc.d/pflog start + &prompt.root; service pflog start Als u andere mogelijkheden van PF nodig heeft dient u ondersteuning voor PF in de kernel te @@ -901,12 +901,7 @@ LOG_ERR – gelogde pakketten die ee /etc/syslog.conf actief te maken kan er opnieuw opgestart worden of is het mogelijk de daemon &man.syslogd.8; een schop te geven zodat /etc/syslog.conf opnieuw - wordt ingelezen met /etc/rc.d/syslogd - reload. Het PID (procesnummer) is te achterhalen - door een overzicht van taken te tonen met - ps -ax. Het PID is het nummer in de - linker kolom voor de regel waarop syslog - staat. + wordt ingelezen met service syslogd reload. Vaak wordt vergeten /etc/newsyslog.conf te wijzigen om het Modified: head/nl_NL.ISO8859-1/books/handbook/jails/chapter.xml ============================================================================== --- head/nl_NL.ISO8859-1/books/handbook/jails/chapter.xml Mon Feb 4 17:28:14 2013 (r40885) +++ head/nl_NL.ISO8859-1/books/handbook/jails/chapter.xml Mon Feb 4 17:32:17 2013 (r40886) @@ -5,7 +5,7 @@ $FreeBSD$ %SOURCE% en_US.ISO8859-1/books/handbook/jails/chapter.xml - %SRCID% 39631 + %SRCID% 40792 --> @@ -401,13 +401,12 @@ jail_www_devf - Het /etc/rc.d/jail bestand kan worden - gebruikt om jails handmatig te starten en te stoppen, mits er - een overeenkomstige set regels bestaat in + &man.service.8; kan worden gebruikt om jails handmatig te starten en + te stoppen, mits er een overeenkomstige verzameling regels bestaat in /etc/rc.conf. - &prompt.root; /etc/rc.d/jail start www -&prompt.root; /etc/rc.d/jail stop www + &prompt.root; service jail start www +&prompt.root; service jail stop www Er is op dit moment geen nette methode om een jail te stoppen. Dit komt omdat de benodigde applicaties die een @@ -932,11 +931,10 @@ jail_www_devfs_enable="YES"In deze fase zijn de jails gebouwd en voorbereid om op te starten. Koppel eerst de benodigde bestandssystemen voor elke jail, en start ze vervolgens door gebruik te - maken van het /etc/rc.d/jail - bestand: + maken van het rc-bestand voor de jail: &prompt.root; mount -a -&prompt.root; /etc/rc.d/jail start +&prompt.root; service jail start @@ -1015,7 +1013,7 @@ jail_www_devfs_enable="YES" Dit is het juiste moment om de jails te stoppen: - &prompt.root; /etc/rc.d/jail stop + &prompt.root; service jail stop @@ -1058,7 +1056,7 @@ jail_www_devfs_enable="YES" &prompt.root; mount -a -&prompt.root; /etc/rc.d/jail start +&prompt.root; service jail start Modified: head/nl_NL.ISO8859-1/books/handbook/linuxemu/chapter.xml ============================================================================== --- head/nl_NL.ISO8859-1/books/handbook/linuxemu/chapter.xml Mon Feb 4 17:28:14 2013 (r40885) +++ head/nl_NL.ISO8859-1/books/handbook/linuxemu/chapter.xml Mon Feb 4 17:32:17 2013 (r40886) @@ -5,7 +5,7 @@ $FreeBSD$ %SOURCE% en_US.ISO8859-1/books/handbook/linuxemu/chapter.xml - %SRCID% 40735 + %SRCID% 40792 --> @@ -683,7 +683,7 @@ done Start de licentieserver. Het volgende script, geïnstalleerd als - /usr/local/etc/rc.d/lmgrd.sh, is een + /usr/local/etc/rc.d/lmgrd, is een gemakkelijke manier om lmgrd op te starten: @@ -877,7 +877,7 @@ FEATURE Maple maplelmg 2000.0831 permane Maak een opstartbestand in - /usr/local/etc/rc.d/flexlm.sh. + /usr/local/etc/rc.d/flexlm. Onderstaand voorbeeld is een gewijzigde versie van het meegeleverde $MATLAB/etc/rc.lm.glnx86. De wijzigingen omvatten bestandslocaties en het starten @@ -906,7 +906,7 @@ exit 0 Het bestand moet uitvoerbaar zijn: - &prompt.root; chmod +x /usr/local/etc/rc.d/flexlm.sh + &prompt.root; chmod +x /usr/local/etc/rc.d/flexlm Ook moet bovenstaande gebruikersnaam vervangen @@ -918,7 +918,7 @@ exit 0 Start de licentiebeheerder op met het commando: - &prompt.root; /usr/local/etc/rc.d/flexlm.sh start + &prompt.root; service flexlm start Modified: head/nl_NL.ISO8859-1/books/handbook/mail/chapter.xml ============================================================================== --- head/nl_NL.ISO8859-1/books/handbook/mail/chapter.xml Mon Feb 4 17:28:14 2013 (r40885) +++ head/nl_NL.ISO8859-1/books/handbook/mail/chapter.xml Mon Feb 4 17:32:17 2013 (r40886) @@ -5,7 +5,7 @@ $FreeBSD$ %SOURCE% en_US.ISO8859-1/books/handbook/mail/chapter.xml - %SRCID% 40216 + %SRCID% 40792 --> @@ -806,7 +806,7 @@ sendmail_msp_queue_enable="NO" /etc/mail/mailer.conf bij benadering het volgende: -sendmail /usr/libexec/sendmail/sendmail + sendmail /usr/libexec/sendmail/sendmail send-mail /usr/libexec/sendmail/sendmail mailq /usr/libexec/sendmail/sendmail newaliases /usr/libexec/sendmail/sendmail @@ -829,13 +829,12 @@ purgestat /usr/libexec/sendmail/sendmail men /etc/mail/mailer.conf als volgt aanpassen: -sendmail /usr/local/supermailer/bin/sendmail-compat + sendmail /usr/local/supermailer/bin/sendmail-compat send-mail /usr/local/supermailer/bin/sendmail-compat mailq /usr/local/supermailer/bin/mailq-compat newaliases /usr/local/supermailer/bin/newaliases-compat hoststat /usr/local/supermailer/bin/hoststat-compat purgestat /usr/local/supermailer/bin/purgestat-compat - @@ -878,8 +877,8 @@ purgestat /usr/local/supermailer/bin/pur BIND - Traditioneel werd dit door BSD BIND resolvers toegestaan - . De huidige versie van BIND die + Traditioneel werd dit door BSD BIND resolvers toegestaan. De + huidige versie van BIND die met &os; wordt geleverd levert niet langer standaard afkortingen voor onvolledig gekwalificeerde domeinnamen anders dan het huidige domein. Dus moet een @@ -1647,7 +1646,7 @@ define(`confDELIVERY_MODE', `deferred')d en start vervolgens het saslauthd-daemon op: - &prompt.root; /usr/local/etc/rc.d/saslauthd start + &prompt.root; service saslauthd start Deze daemon fungeert als een onderhandelaar voor sendmail die zich tegen de &os; Modified: head/nl_NL.ISO8859-1/books/handbook/multimedia/chapter.xml ============================================================================== --- head/nl_NL.ISO8859-1/books/handbook/multimedia/chapter.xml Mon Feb 4 17:28:14 2013 (r40885) +++ head/nl_NL.ISO8859-1/books/handbook/multimedia/chapter.xml Mon Feb 4 17:32:17 2013 (r40886) @@ -5,7 +5,7 @@ $FreeBSD$ %SOURCE% en_US.ISO8859-1/books/handbook/multimedia/chapter.xml - %SRCID% 40784 + %SRCID% 40792 --> @@ -1742,7 +1742,7 @@ bktr0: Pinnacle/Miro TV, Philips SECAM t Start de achterkant: &prompt.root; echo 'mythbackend_enable="YES"' >> /etc/rc.conf -&prompt.root; /usr/local/etc/rc.d/mythbackend start +&prompt.root; service mythbackend start Modified: head/nl_NL.ISO8859-1/books/handbook/network-servers/chapter.xml ============================================================================== --- head/nl_NL.ISO8859-1/books/handbook/network-servers/chapter.xml Mon Feb 4 17:28:14 2013 (r40885) +++ head/nl_NL.ISO8859-1/books/handbook/network-servers/chapter.xml Mon Feb 4 17:32:17 2013 (r40886) @@ -5,7 +5,7 @@ $FreeBSD$ %SOURCE% en_US.ISO8859-1/books/handbook/network-servers/chapter.xml - %SRCID% 40744 + %SRCID% 40792 --> @@ -185,7 +185,7 @@ inetd bij het opstarten van een systeem wel of niet ingeschakeld. Het commando: - &prompt.root; /etc/rc.d/inetd rcvar + &prompt.root; service inetd rcvar kan gedraaid worden om de huidige effectieve instellingen weer te geven. @@ -285,7 +285,7 @@ Het instellingenbestand van <application>inetd</application> herladen - &prompt.root; /etc/rc.d/inetd reload + &prompt.root; service inetd reload Iedere regel in het bestand met instellingen heeft @@ -839,7 +839,7 @@ mountd_flags="-r" of door het &man.rc.8; script mountd met de juiste parameter aan te roepen: - &prompt.root; /etc/rc.d/mountd onereload + &prompt.root; service mountd onereload Raadpleeg voor meer informatie over het gebruik van rc-scripts. @@ -909,8 +909,8 @@ rpc_statd_enable="YES" Start de applicatie met: - &prompt.root; /etc/rc.d/lockd start -&prompt.root; /etc/rc.d/statd start + &prompt.root; service lockd start +&prompt.root; service statd start Als echt op slot zetten tussen de NFS-cliënten en de @@ -1666,7 +1666,7 @@ Exports list on foobar: laatste stap, voor het initialiseren van de NIS-afbeeldingen, de daemon ypserv handmatig: - &prompt.root; /etc/rc.d/ypserv start + &prompt.root; service ypserv start @@ -1965,7 +1965,7 @@ nis_client_enable="YES" commando's als supergebruiker uit: &prompt.root; /etc/netstart -&prompt.root; /etc/rc.d/ypbind start +&prompt.root; service ypbind start Na het afronden van deze stappen zou met ypcat passwd de passwd map van de NIS-server te zien @@ -3155,7 +3155,7 @@ dhcpd_ifaces="dc0" Daarna kunt u doorgaan met het starten van de server door het volgende commando te geven: - &prompt.root; /usr/local/etc/rc.d/isc-dhcpd start + &prompt.root; service isc-dhcpd start Als er later wijzigingen in de instellingen gemaakt moeten worden, dan is het belangrijk te onthouden dat het sturen van @@ -3544,7 +3544,7 @@ dhcpd_ifaces="dc0" (127.0.0.1). Gebruik het volgende commando om de server eenmaal met deze configuratie te starten: - &prompt.root; /etc/rc.d/named onestart + &prompt.root; service named onestart Om er zeker van te zijn dat de daemon named elke keer bij het opstarten @@ -4806,7 +4806,7 @@ $include Kexample.com.+005+nnnnn.ZSK.key De port www/apache2 installeert een &man.rc.8;-script dat helpt met het starten, stoppen en herstarten - van Apache en is te vinden in de map + van Apache en is te vinden in /usr/local/etc/rc.d/. Om Apache met het systeem mee te @@ -4829,8 +4829,6 @@ $include Kexample.com.+005+nnnnn.ZSK.key &man.service.8; door één van de volgende commando's op te geven: - &prompt.root; /usr/local/etc/rc.d/apache22 configtest - &prompt.root; service apache22 configtest @@ -4841,10 +4839,7 @@ $include Kexample.com.+005+nnnnn.ZSK.key Als Apache geen instellingsfouten meldt, kan Apache httpd - gestart worden met dezelfde &man.rc.8;- en - &man.service.8;-mechanismen: - - &prompt.root; /usr/local/etc/rc.d/apache22 start + gestart worden met &man.service.8;: &prompt.root; service apache22 start @@ -5283,7 +5278,7 @@ $include Kexample.com.+005+nnnnn.ZSK.key volgende commando als root uit te voeren: - &prompt.root; /etc/rc.d/ftpd start + &prompt.root; service ftpd start Nu kan aangemeld worden op de FTP-server met: @@ -5588,7 +5583,7 @@ $include Kexample.com.+005+nnnnn.ZSK.key Samba op elk moment te starten door dit te typen: - &prompt.root; /usr/local/etc/rc.d/samba start + &prompt.root; service samba start Starting SAMBA: removing stale tdbs : Starting nmbd. Starting smbd. @@ -5608,7 +5603,7 @@ Starting smbd. Samba kan op ieder moment gestopt worden met: - &prompt.root; /usr/local/etc/rc.d/samba stop + &prompt.root; service samba stop Samba is een complexe softwaresuite met functionaliteit waarmee verregaande integratie @@ -5999,7 +5994,7 @@ syslogd_flags="-a logclient.example.com Nu dient het syslogd-daemon herstart en geverifieerd worden: - &prompt.root; /etc/rc.d/syslogd restart + &prompt.root; service syslogd restart &prompt.root; pgrep syslog Als er een PID wordt teruggegeven, dan is @@ -6074,7 +6069,7 @@ syslogd_flags="-s -v -v"Eenmaal toegevoegd moet syslogd worden herstart zodat de veranderingen effect hebben: - &prompt.root; /etc/rc.d/syslogd restart + &prompt.root; service syslogd restart Om te testen of logberichten over het netwerk worden verzonden, wordt &man.logger.1; op de cliënt gebruikt om @@ -6111,7 +6106,7 @@ syslogd_flags="-s -v -v"syslogd_flags="-d -a logclien.example.com -v -v" - &prompt.root; /etc/rc.d/syslogd restart + &prompt.root; service syslogd restart Debuggegevens zoals de volgende zullen meteen na de herstart over het scherm vliegen: @@ -6137,7 +6132,7 @@ rejected in rule 0 due to name mismatch. wijzigingen zijn gemaakt, wordt er herstart met de verwachte resultaten: - &prompt.root; /etc/rc.d/syslogd restart + &prompt.root; service syslogd restart logmsg: pri 56, flags 4, from logserv.example.com, msg syslogd: restart syslogd: restarted logmsg: pri 6, flags 4, from logserv.example.com, msg syslogd: kernel boot file is /boot/kernel/kernel Modified: head/nl_NL.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml ============================================================================== --- head/nl_NL.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml Mon Feb 4 17:28:14 2013 (r40885) +++ head/nl_NL.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml Mon Feb 4 17:32:17 2013 (r40886) @@ -5,7 +5,7 @@ $FreeBSD$ %SOURCE% en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml - %SRCID% 40778 + %SRCID% 40792 --> @@ -3155,7 +3155,7 @@ water.CS.Example localhost.Example. UGH volgende commando als root uitvoeren: - &prompt.root; /etc/rc.d/routing start + &prompt.root; service routing start Raadpleeg aub over het configureren van de &os; kernel voor meer hulp over het Modified: head/nl_NL.ISO8859-1/books/handbook/security/chapter.xml ============================================================================== --- head/nl_NL.ISO8859-1/books/handbook/security/chapter.xml Mon Feb 4 17:28:14 2013 (r40885) +++ head/nl_NL.ISO8859-1/books/handbook/security/chapter.xml Mon Feb 4 17:32:17 2013 (r40886) @@ -5,7 +5,7 @@ $FreeBSD$ %SOURCE% en_US.ISO8859-1/books/handbook/security/chapter.xml - %SRCID% 40749 + %SRCID% 40792 --> @@ -1583,10 +1583,10 @@ Enter secret pass phrase: < qpopper : ALL : allow Nadat deze regel is toegevoegd moet - inetd herstart worden. Dit gaat met - het commando &man.kill.1; of met de parameter - restart met - /etc/rc.d/inetd. + inetd herstart worden door gebruik te maken + van &man.service.8;: + + &prompt.root; service inetd restart @@ -1961,8 +1961,8 @@ Password: xxxxxxxxxxxxxxxx Nu kan de KDC dienst gestart worden - met /etc/rc.d/kerberos start en - /etc/rc.d/kadmind start. Op dit moment + met service kerberos start en + service kadmind start. Op dit moment draait er nog geen enkele daemon die gebruik maakt van Kerberos. Bevestiging dat KDC draait is te krijgen door een ticket te @@ -2086,7 +2086,7 @@ kadmin> exittelnet geactiveerd door de volgende regel in /etc/inetd.conf te zetten en dan &man.inetd.8; te herstarten met - /etc/rc.d/inetd restart: + service inetd restart: telnet stream tcp nowait root /usr/libexec/telnetd telnetd -a user @@ -3341,11 +3341,11 @@ racoon_enable="yes" Hierdoor wordt &man.sshd.8; geladen, het daemonprogramma voor OpenSSH, als het systeem de - volgende keer opstart. Als alternatief is het mogelijk om het - &man.rc.8;-script /etc/rc.d/sshd te + volgende keer opstart. Als alternatief is het mogelijk om + &man.rc.8; te gebruiken om OpenSSH te starten: - &prompt.root; /etc/rc.d/sshd start + &prompt.root; service sshd start @@ -3752,7 +3752,7 @@ user@unfirewalled-system.example.org's p /etc/ssh/sshd_config dienen de bestanden in &man.sshd.8; geladen te worden: - &prompt.root; /etc/rc.d/sshd reload + &prompt.root; service sshd reload Modified: head/nl_NL.ISO8859-1/books/handbook/virtualization/chapter.xml ============================================================================== --- head/nl_NL.ISO8859-1/books/handbook/virtualization/chapter.xml Mon Feb 4 17:28:14 2013 (r40885) +++ head/nl_NL.ISO8859-1/books/handbook/virtualization/chapter.xml Mon Feb 4 17:32:17 2013 (r40886) @@ -5,7 +5,7 @@ $FreeBSD$ %SOURCE% en_US.ISO8859-1/books/handbook/virtualization/chapter.xml - %SRCID% 40780 + %SRCID% 40792 --> @@ -1245,7 +1245,7 @@ add path 'usb/*' mode 0660 group operato Herstart vervolgens devfs: - &prompt.root; /etc/rc.d/devfs restart + &prompt.root; service devfs restart USB kan nu in het gast-besturingssysteem worden aangezet. USB-apparaten zouden zichtbaar moeten zijn in de voorkeuren van @@ -1292,7 +1292,7 @@ add path 'usb/*' mode 0660 group operato perm xpt0 0660 perm pass* 0660 - &prompt.root; /etc/rc.d/devfs restart + &prompt.root; service devfs restart - The FreeBSD Booting Process + The &os; Booting Process Synopsis @@ -16,31 +16,31 @@ The process of starting a computer and loading the operating system is referred to as the bootstrap process, - or simply booting. FreeBSD's boot process + or simply booting. &os;'s boot process provides a great deal of flexibility in customizing what happens - when you start the system, allowing you to select from different - operating systems installed on the same computer, or even - different versions of the same operating system or installed - kernel. - - This chapter details the configuration options you can set - and how to customize the FreeBSD boot process. This includes - everything that happens until the FreeBSD kernel has started, - probed for devices, and started &man.init.8;. If you are not - quite sure when this happens, it occurs when the text color - changes from bright white to grey. + when the system starts, including the ability to select from + different operating systems installed on the same computer, + different versions of the same operating system, or a different + installed kernel. + + This chapter details the configuration options that can + be set. It demonstrates how to customize the &os; boot + process, including everything that happens until the &os; kernel + has started, probed for devices, and started &man.init.8;. This + occurs when the text color of the boot messages changes from + bright white to grey. - After reading this chapter, you will know: + After reading this chapter, you will recognize: - What the components of the FreeBSD bootstrap system are, - and how they interact. + The components of the &os; bootstrap system and how they + interact. - The options you can give to the components in the - FreeBSD bootstrap to control the boot process. + The options that can be passed to the components in the + &os; bootstrap in order to control the boot process. @@ -49,9 +49,7 @@ - x86 Only - - This chapter only describes the boot process for FreeBSD + This chapter only describes the boot process for &os; running on Intel x86 systems. @@ -62,7 +60,7 @@ Turning on a computer and starting the operating system poses an interesting dilemma. By definition, the computer does not know how to do anything until the operating system is - started. This includes running programs from the disk. So if + started. This includes running programs from the disk. If the computer can not run a program from the disk without the operating system, and the operating system programs are on the disk, how is the operating system started? @@ -102,7 +100,7 @@ with the user. In this case the boot manager usually has more code in the first track of the disk or within some OS's file system. (A boot manager is sometimes also - called a boot loader, but FreeBSD uses that + called a boot loader, but &os; uses that term for a later stage of booting.) Popular boot managers include boot0 (aka Boot Easy, the standard &os; boot @@ -111,30 +109,28 @@ LILO. (Only boot0 fits within the MBR.) - If you have only one operating system installed on your - disks then a standard PC MBR will suffice. This MBR searches - for the first bootable (aka active) slice on the disk, and - then runs the code on that slice to load the remainder of the - operating system. The MBR installed by &man.fdisk.8;, by - default, is such an MBR. It is based on + If only one operating system is installed, a standard PC MBR + will suffice. This MBR searches for the first bootable (active) + slice on the disk, and then runs the code on that slice to load + the remainder of the operating system. By default, the MBR + installed by &man.fdisk.8; is such an MBR and is based on /boot/mbr. - If you have installed multiple operating systems on your - disks then you can install a different boot manager, one that - can display a list of different operating systems, and allows - you to choose the one to boot from. Two of these are discussed - in the next subsection. + If multiple operating systems are present, a different boot + manager can be installed which displays the list of operating + systems so that the user can choose which one to boot from. Two + boot managers are discussed in the next subsection. - The remainder of the FreeBSD bootstrap system is divided + The remainder of the &os; bootstrap system is divided into three stages. The first stage is run by the MBR, which knows just enough to get the computer into a specific state and run the second stage. The second stage can do a little bit more, before running the third stage. The third stage finishes the task of loading the operating system. The work is split - into these three stages because the PC standards put limits on - the size of the programs that can be run at stages one and two. - Chaining the tasks together allows FreeBSD to provide a more - flexible loader. + into three stages because PC standards put limits on the size of + the programs that can be run at stages one and two. Chaining + the tasks together allows &os; to provide a more flexible + loader. kernel init @@ -145,9 +141,8 @@ process &man.init.8;, which then makes sure the disks are in a usable state. &man.init.8; then starts the user-level resource configuration which mounts file systems, sets up network cards - to communicate on the network, and generally starts all the - processes that usually are run on a FreeBSD system at - startup. + to communicate on the network, and starts the processes which + have been configured to run on a &os; system at startup. @@ -163,60 +158,54 @@ The code in the MBR or boot manager is sometimes referred to as stage zero of the boot process. - This subsection discusses two of the boot managers previously - mentioned: boot0 and + This section discusses two boot managers: + boot0 and LILO. The <application>boot0</application> Boot Manager: - The MBR installed by FreeBSD's installer or - &man.boot0cfg.8;, by default, is based on - /boot/boot0. (The - boot0 program is very simple, - since the program in the MBR can only be - 446 bytes long because of the slice table and - 0x55AA identifier at the end of the MBR.) - If you have installed boot0 and - multiple operating systems on your hard disks, then you will - see a display similar to this one at boot - time: + The MBR installed by &os;'s installer or + &man.boot0cfg.8; is based on + /boot/boot0. The size and capability + of boot0 is restricted to 446 + bytes due to the slice table and 0x55AA + identifier at the end of the MBR. If + boot0 and multiple operating + systems are installed, a message similar to this example + will be displayed at boot time: <filename>boot0</filename> Screenshot - F1 DOS + F1 Windows F2 FreeBSD -F3 Linux -F4 ?? -F5 Drive 1 Default: F2 - Other operating systems, in particular &windows;, have - been known to overwrite an existing MBR with their own. If - this happens to you, or you want to replace your existing MBR - with the FreeBSD MBR then use the following command: + Other operating systems, in particular &windows;, will + overwrite an existing MBR if they are installed after &os;. + If this happens, or you want to replace the existing MBR + with the &os; MBR, use the following command: &prompt.root; fdisk -B -b /boot/boot0 device - where device is the device that - you boot from, such as ad0 for the - first IDE disk, ad2 for the first IDE - disk on a second IDE controller, da0 - for the first SCSI disk, and so on. Or, if you want a custom - configuration of the MBR, use &man.boot0cfg.8;. + where device is the boot disk, + such as ad0 for the first IDE disk, + ad2 for the first IDE disk on a + second IDE controller, or da0 + for the first SCSI disk. To create a custom configuration of + the MBR, refer to &man.boot0cfg.8;. The LILO Boot Manager: To install this boot manager so it will also boot - FreeBSD, first start Linux and add the following to your - existing /etc/lilo.conf configuration - file: + &os;, boot into Linux and add the following to the existing + /etc/lilo.conf configuration: other=/dev/hdXY @@ -224,30 +213,29 @@ table=/dev/hdX loader=/boot/chain.b label=FreeBSD - In the above, specify FreeBSD's primary partition and - drive using Linux specifiers, replacing - X with the Linux drive letter and - Y with the Linux primary partition - number. If you are using a SCSI drive, you - will need to change /dev/hd to read - something similar to /dev/sd. The + Specify &os;'s primary partition and drive using Linux + specifiers, replacing X with the + Linux drive letter and Y with the + Linux primary partition number. For a SCSI + drive, change /dev/hd to + /dev/sd. The line can be omitted if - you have both operating systems on the same drive. Now run - /sbin/lilo -v to commit your new - changes to the system; this should be verified by checking its - screen messages. + both operating systems are installed on the same drive. Next, + run /sbin/lilo -v to commit the new + changes. Verify these are correct by checking the screen + messages. Stage One, <filename>/boot/boot1</filename>, and Stage Two, <filename>/boot/boot2</filename> - Conceptually the first and second stages are part of the + Conceptually, the first and second stages are part of the same program, on the same area of the disk. Because of space - constraints they have been split into two, but you would - always install them together. They are copied from the - combined file /boot/boot by the installer - or bsdlabel (see below). + constraints, they have been split into two, but are always + installed together. They are copied from the combined + /boot/boot by the installer or + bsdlabel. They are located outside file systems, in the first track of the boot slice, starting with the first sector. This is @@ -259,20 +247,18 @@ label=FreeBSD boot1 is very simple, since it can only be 512 bytes in size, and knows just enough about the - FreeBSD bsdlabel, which stores + &os; bsdlabel, which stores information about the slice, to find and execute boot2. boot2 is slightly more sophisticated, - and understands the FreeBSD file system enough to find files - on it, and can provide a simple interface to choose the kernel - or loader to run. - - Since the loader is - much more sophisticated, and provides a nice easy-to-use - boot configuration, boot2 usually runs - it, but previously it - was tasked to run the kernel directly. + and understands the &os; file system enough to find files, and + can provide a simple interface to choose the kernel or loader + to run. + + loader is much more + sophisticated and provides a boot configuration which is run + by boot2. <filename>boot2</filename> Screenshot @@ -282,25 +268,26 @@ Default: 0:ad(0,a)/boot/loader boot: - If you ever need to replace the installed - boot1 and boot2 use - &man.bsdlabel.8;: + &man.bsdlabel.8; can be used to replace the installed + boot1 and + boot2: &prompt.root; bsdlabel -B diskslice where diskslice is the disk and - slice you boot from, such as ad0s1 + slice to boot from, such as ad0s1 for the first slice on the first IDE disk. Dangerously Dedicated Mode - If you use just the disk name, such as - ad0, in the &man.bsdlabel.8; - command you will create a dangerously dedicated disk, - without slices. This is almost certainly not what you want - to do, so make sure you double check the &man.bsdlabel.8; - command before you press Return. + If just the disk name is used, such as + ad0, &man.bsdlabel.8; will create a + dangerously dedicated disk, without slices. + This is probably not the desired action, so double check the + diskslice passed to + &man.bsdlabel.8; before pressing + Return. @@ -313,16 +300,16 @@ boot: bootstrap, and is located on the file system, usually as /boot/loader. - The loader is intended as a user-friendly method for - configuration, using an easy-to-use built-in command set, - backed up by a more powerful interpreter, with a more complex - command set. + The loader is intended as an interactive method for + configuration, using a built-in command set, backed up by a + more powerful interpreter which has a more complex command + set. Loader Program Flow During initialization, the loader will probe for a - console and for disks, and figure out what disk it is + console and for disks, and figure out which disk it is booting from. It will set variables accordingly, and an interpreter is started where user commands can be passed from a script or interactively. @@ -342,16 +329,16 @@ boot: Finally, by default, the loader issues a 10 second wait for key presses, and boots the kernel if it is not interrupted. If interrupted, the user is presented with a - prompt which understands the easy-to-use command set, where - the user may adjust variables, unload all modules, load - modules, and then finally boot or reboot. + prompt which understands the command set, where the user may + adjust variables, unload all modules, load modules, and then + finally boot or reboot. Loader Built-In Commands These are the most commonly used loader commands. For a - complete discussion of all available commands, please see + complete discussion of all available commands, refer to &man.loader.8;. @@ -372,11 +359,10 @@ boot: kernelname - Immediately proceeds to boot the kernel, with the - given options, if any, and with the kernel name given, - if it is. Providing a kernel name on the command-line - is only applicable after an - unload command has been issued, + Immediately proceeds to boot the kernel, with any + specified options or kernel name. Providing a kernel + name on the command-line is only applicable after an + unload command has been issued; otherwise the previously-loaded kernel will be used. @@ -387,10 +373,10 @@ boot: Goes through the same automatic configuration of - modules based on variables as what happens at boot. - This only makes sense if you use - unload first, and change some - variables, most commonly kernel. + modules based on specified variables, most commonly + kernel. This only makes sense if + unload is used first, before + changing some variables. @@ -401,8 +387,8 @@ boot: Shows help messages read from /boot/loader.help. If the topic - given is index, then the list of - available topics is given. + given is index, the list of + available topics is displayed. @@ -412,7 +398,7 @@ boot: Processes the file with the given filename. The - file is read in, and interpreted line by line. An + file is read in and interpreted line by line. An error immediately stops the include command. @@ -424,8 +410,9 @@ boot: Loads the kernel, kernel module, or file of the - type given, with the filename given. Any arguments - after filename are passed to the file. + type given, with the specified filename. Any + arguments after filename + are passed to the file. @@ -436,8 +423,8 @@ boot: Displays a listing of files in the given path, or the root directory, if the path is not specified. If - is specified, file sizes will be - shown too. + is specified, file sizes will + also be shown. @@ -508,15 +495,14 @@ boot: single-user mode - To boot your usual kernel, but in single-user - mode: + To boot the usual kernel in single-user mode: boot -s - To unload your usual kernel and modules, and then - load just your old (or another) kernel: + To unload the usual kernel and modules, and then + load the previous or another kernel: kernel.old @@ -525,14 +511,14 @@ boot: unload load kernel.old - You can use kernel.GENERIC to - refer to the generic kernel that comes on the install - disk, or kernel.old to refer to - your previously installed kernel (when you have upgraded - or configured your own kernel, for example). + Use kernel.GENERIC to refer to + the default kernel that comes with an installation, or + kernel.old to refer to the + previously installed kernel before a system upgrade or + before configuring a custom kernel. - Use the following to load your usual modules with + Use the following to load the usual modules with another kernel: unload @@ -541,9 +527,8 @@ boot: - To load a kernel configuration script (an automated - script which does the things you would normally do in - the kernel boot-time configurator): + To load an automated kernel configuration + script: load -t userconfig_script /boot/kernel.conf @@ -563,89 +548,58 @@ boot: Boot Time Splash Screens - The splash screen creates a more visually appealing boot - screen compared to the original boot messages. This screen - will be displayed until a console login prompt or an X - display manager offers a login prompt. + The splash screen creates an alternate boot screen. The + splash screen hides all the boot probe messages and service + startup messages before displaying either a command line or + graphical login prompt. There are two basic environments available in &os;. The first is the default legacy virtual console command line environment. After the system finishes booting, a console login prompt is presented. The second environment is the - X11 Desktop graphical environment. After - X11 and one of the - graphical - desktop environments, such as - GNOME, - KDE, or - XFce are installed, the X11 - desktop can be launched by using - startx. - - Some users prefer the X11 graphical login screen over - the traditional text based login prompt. Display managers - like XDM for &xorg;, - gdm for - GNOME, and - kdm for - KDE (and any other from the Ports - Collection) provide a graphical login screen in - place of the console login prompt. After a successful - login, they present the user with a graphical - desktop. - - In the command line environment, the splash screen would - hide all the boot probe messages and task startup messages - before displaying the login prompt. In X11 environment, the - users would get a visually clearer system start up - experience resembling something closer to what a - (µsoft; &windows; or non-unix type system) user would - experience. + graphical environment provided by + Xorg. Refer to that chapter for + more information on how to install and configure a graphical + display manager and a graphical login manager. Splash Screen Function - The splash screen function supports 256-color + The splash screen function supports 256-colors in the bitmap (.bmp), ZSoft PCX (.pcx), or - TheDraw (.bin) files. - In addition, the splash image files must have a resolution - of 320 by 200 pixels or less to work on standard VGA - adapters. + TheDraw (.bin) formats. The splash + image files must have a resolution of 320 by 200 pixels or + less in order to work on standard VGA adapters. To use larger images, up to the maximum resolution of - 1024 by 768 pixels, activate the VESA - support included in &os;. This can be enabled by loading - the VESA module during system boot, or - adding a VESA kernel configuration - option and building a custom kernel (see ). The VESA - support gives users the ability to display a splash screen - image that fills the whole display screen. + 1024 by 768 pixels, load the VESA + module during system boot. For a custom kernel, include the + VESA kernel configuration option. + Loading VESA support provides the + ability to display a splash screen image that fills the + whole display screen. While the splash screen is being displayed during the booting process, it can be turned off any time by hitting any key on the keyboard. The splash screen also defaults to being a screen - saver outside of X11. After a time period of non-use the - screen will change to the splash screen and cycle through - steps of changing intensity of the image, from bright to a - very dark and over again. This default splash screen - (screen saver) behavior could be overridden by adding a + saver outside. After a time period of non-use, the splash + screen will be displayed and will cycle through steps of + changing intensity of the image, from bright to very dark + and over again. The configuration of the splash screen + saver can be overridden by adding a saver= line to - /etc/rc.conf. Option - saver= has several built-in screen - savers to choose from, the full list can be found in the - &man.splash.4; manual page. The default screen saver is - called warp. Note that the - saver= option specified in - /etc/rc.conf only applies to virtual - consoles. It has no effect on X11 display - managers. + /etc/rc.conf. Several built-in + screen savers are available and described in + &man.splash.4;. The saver= option only + applies to virtual consoles and has no effect on graphical + display managers. A few boot loader messages, including the boot options - menu and a timed wait count down prompt are displayed at + menu and a timed wait count down prompt, are displayed at boot time, even when the splash screen is enabled. Sample splash screen files can be downloaded from the @@ -660,15 +614,14 @@ boot: Enabling the Splash Screen Function - The splash screen (.bmp, - .pcx, or .bin) - file has to be placed on the root partition, for example - in the /boot - directory. - - For default boot display resolution (256-color, 320 by - 200 pixels, or less), edit - /boot/loader.conf, so it contains the + The splash screen .bmp, + .pcx, or .bin + image has to be placed on the root partition, for example + in /boot. + + For the default boot display resolution of 256-colors + and 320 by 200 pixels or less, edit + /boot/loader.conf so it contains the following: splash_bmp_load="YES" @@ -685,19 +638,19 @@ splash_bmp_load="YES" bitmap_load="YES" bitmap_name="/boot/splash.bmp" - The above assumes that + This example assumes that /boot/splash.bmp - is used for splash screen. When a PCX - file is desired, use the following statements, plus the - vesa_load="YES" line depending on the - resolution. + is used for the splash screen. To use a + PCX file, use the following statements, + plus the vesa_load="YES" line, + depending on the resolution: splash_pcx_load="YES" bitmap_load="YES" bitmap_name="/boot/splash.pcx" - In version 8.3 another option is to use ascii art in - Beginning with &os; 8.3, another option is to use + ASCII art in TheDraw format. @@ -707,14 +660,14 @@ bitmap_name="/boot/splash.b The file name is not restricted to splash as shown in the above example. It - can be anything as long as it is one of the above types - such as, + can be anything as long as it is one of the supported + types such as, splash_640x400.bmp or bluewave.pcx. - Some other interesting - loader.conf options: + Other interesting + loader.conf options include: @@ -737,13 +690,13 @@ bitmap_name="/boot/splash.b This will replace the default words &os;, which are displayed to the right of the boot options menu with the colored - beastie logo like releases in the past had. + beastie logo. - For more information, please see the &man.splash.4;, - &man.loader.conf.5;, and &man.vga.4; manual pages. + For more information, refer to &man.splash.4;, + &man.loader.conf.5;, and &man.vga.4;. @@ -757,10 +710,10 @@ bitmap_name="/boot/splash.b boot interaction - Once the kernel is loaded by either loader (as usual) or boot2 (bypassing the loader), it - examines its boot flags, if any, and adjusts its behavior as + Once the kernel is loaded by either the default loader or by boot2 which bypasses the loader, + it examines its boot flags, if any, and adjusts its behavior as necessary. @@ -778,7 +731,7 @@ bitmap_name="/boot/splash.b - during kernel initialization, ask for the device + During kernel initialization, ask for the device to mount as the root file system. @@ -787,7 +740,7 @@ bitmap_name="/boot/splash.b - boot from CDROM. + Boot from CDROM. @@ -795,8 +748,8 @@ bitmap_name="/boot/splash.b - run UserConfig, the boot-time kernel - configurator + Run UserConfig, the boot-time kernel + configurator. @@ -804,7 +757,7 @@ bitmap_name="/boot/splash.b - boot into single-user mode + Boot into single-user mode. @@ -812,14 +765,14 @@ bitmap_name="/boot/splash.b - be more verbose during kernel startup + Be more verbose during kernel startup. - There are other boot flags, read &man.boot.8; for more - information on them. + Refer to &man.boot.8; for more information on the other + boot flags. @@ -848,27 +801,26 @@ bitmap_name="/boot/splash.b device.hints - During initial system startup, the boot &man.loader.8; will - read the &man.device.hints.5; file. This file stores kernel - boot information known as variables, sometimes referred to as + During initial system startup, the boot &man.loader.8; reads + &man.device.hints.5;. This file stores kernel boot information + known as variables, sometimes referred to as device hints. These device hints are used by device drivers for device configuration. - Device hints may also be specified at the - - Stage 3 boot loader prompt. Variables can be added using - set, removed with unset, - and viewed with the show commands. Variables - set in /boot/device.hints can be - overridden here also. Device hints entered at the boot loader - are not permanent and will be forgotten on the next - reboot. + Device hints may also be specified at the Stage 3 boot loader prompt. + Variables can be added using set, removed + with unset, and viewed + show. Variables set in + /boot/device.hints can also be overridden. + Device hints entered at the boot loader are not permanent and + will not be applied on the next reboot. - Once the system is booted, the &man.kenv.1; command can be - used to dump all of the variables. + Once the system is booted, &man.kenv.1; can be used to dump + all of the variables. The syntax for /boot/device.hints - is one variable per line, using the standard hash + is one variable per line, using the hash # as comment markers. Lines are constructed as follows: @@ -878,7 +830,7 @@ bitmap_name="/boot/splash.b set hint.driver.unit.keyword=value - driver is the device driver name, + where driver is the device driver name, unit is the device driver unit number, and keyword is the hint keyword. The keyword may consist of the following options: @@ -920,10 +872,10 @@ bitmap_name="/boot/splash.b - Device drivers may accept (or require) more hints not listed - here, viewing their manual page is recommended. For more - information, consult the &man.device.hints.5;, &man.kenv.1;, - &man.loader.conf.5;, and &man.loader.8; manual pages. + Since device drivers may accept or require more hints not + listed here, viewing a driver's manual page is recommended. + For more information, refer to &man.device.hints.5;, + &man.kenv.1;, &man.loader.conf.5;, and &man.loader.8;. @@ -944,10 +896,10 @@ bitmap_name="/boot/splash.b The automatic reboot sequence makes sure that the file systems available on the system are consistent. If they are - not, and &man.fsck.8; cannot fix the inconsistencies, - &man.init.8; drops the system into - single-user mode for - the system administrator to take care of the problems + not, and &man.fsck.8; cannot fix the inconsistencies of a UFS + file system, &man.init.8; drops the system into + single-user mode so + that the system administrator can resolve the problem directly. @@ -957,21 +909,19 @@ bitmap_name="/boot/splash.b single-user mode console - This mode can be reached through the - automatic reboot - sequence, or by the user booting with the - option or setting the - boot_single variable in + This mode can be reached through the automatic reboot sequence, + the user booting with , or by setting + the boot_single variable in loader. - It can also be reached by calling &man.shutdown.8; without - the reboot () or halt () - options, from multi-user - mode. + It can also be reached by calling &man.shutdown.8; from + multi-user mode without + including or . If the system console is set to insecure in /etc/ttys, - then the system prompts for the root + the system will prompt for the root password before initiating single-user mode. @@ -986,13 +936,12 @@ console none - An insecure console means that you - consider your physical security to the console to be - insecure, and want to make sure only someone who knows the - root password may use single-user mode, - and it does not mean that you want to run your console - insecurely. Thus, if you want security, choose - insecure, not + An insecure console means that + physical security to the console is considered to be + insecure, so only someone who knows the + root password may use single-user mode. + Thus, to add this measure of security, choose + insecure, instead of the default of secure. @@ -1002,8 +951,8 @@ console none multi-user mode - If &man.init.8; finds your file systems to be in order, or - once the user has finished in If &man.init.8; finds the file systems to be in order, or + once the user has finished their commands in single-user mode, the system enters multi-user mode, in which it starts the resource configuration of the system. @@ -1018,14 +967,13 @@ console none /etc/defaults/rc.conf, and system-specific details from /etc/rc.conf, and then proceeds to - mount the system file systems mentioned in - /etc/fstab, start up networking - services, start up miscellaneous system daemons, and - finally runs the startup scripts of locally installed - packages. + mount the system file systems listed in + /etc/fstab. It starts up networking + services, miscellaneous system daemons, then the startup + scripts of locally installed packages. - The &man.rc.8; manual page is a good reference to the - resource configuration system, as is examining the scripts + To learn more about the resource configuration system, + refer to &man.rc.8; and examine the scripts themselves. @@ -1038,27 +986,26 @@ console none shutdown - Upon controlled shutdown, via &man.shutdown.8;, + Upon controlled shutdown using &man.shutdown.8;, &man.init.8; will attempt to run the script /etc/rc.shutdown, and then proceed to send all processes the TERM signal, and subsequently the KILL signal to any that do - not terminate timely. + not terminate in a timely manner. - To power down a FreeBSD machine on architectures and systems - that support power management, use the command - shutdown -p now to turn the power off - immediately. To just reboot a FreeBSD system, just use - shutdown -r now. You need to be - root or a member of - operator group to run &man.shutdown.8;. - The &man.halt.8; and &man.reboot.8; commands can also be used, - please refer to their manual pages and to &man.shutdown.8;'s one - for more information. + To power down a &os; machine on architectures and systems + that support power management, use shutdown -p + now to turn the power off immediately. To reboot a + &os; system, use shutdown -r now. One must + be root or a member of the + operator group in order to run + &man.shutdown.8;. One can also use &man.halt.8; and + &man.reboot.8;. Refer to their manual pages and to + &man.shutdown.8; for more information. - Power management requires &man.acpi.4; support in the - kernel or loaded as module for. + Power management requires &man.acpi.4; to be loaded as + a module or staticly compiled into a custom kernel. From owner-svn-doc-head@FreeBSD.ORG Mon Feb 4 22:56:59 2013 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 15415847; Mon, 4 Feb 2013 22:56:59 +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 BCFD67B4; Mon, 4 Feb 2013 22:56:58 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.6/8.14.6) with ESMTP id r14Muv2T017379; Mon, 4 Feb 2013 15:56:57 -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 r14MuvGb017376; Mon, 4 Feb 2013 15:56:57 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Mon, 4 Feb 2013 15:56:57 -0700 (MST) From: Warren Block To: Dru Lavigne Subject: Re: svn commit: r40887 - head/en_US.ISO8859-1/books/handbook/boot In-Reply-To: <201302042221.r14MLs5Z012993@svn.freebsd.org> Message-ID: References: <201302042221.r14MLs5Z012993@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, 04 Feb 2013 15:56:57 -0700 (MST) Cc: svn-doc-head@freebsd.org, svn-doc-all@freebsd.org, doc-committers@freebsd.org X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 22:56:59 -0000 On Mon, 4 Feb 2013, Dru Lavigne wrote: > Author: dru > Date: Mon Feb 4 22:21:54 2013 > New Revision: 40887 > URL: http://svnweb.freebsd.org/changeset/doc/40887 > > Log: > This patch addresses the following: > > - replaces FreeBSD with &os; > > - rewording to replace "you" > > - updated the F1 example > > <filename>boot0</filename> Screenshot > > - F1 DOS > + F1 Windows > F2 FreeBSD > -F3 Linux > -F4 ?? > -F5 Drive 1 > Actually, boot0 only shows "Win" for an NTFS slice. At least in 9-STABLE. From owner-svn-doc-head@FreeBSD.ORG Tue Feb 5 01:34:24 2013 Return-Path: Delivered-To: svn-doc-head@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 3F765A64; Tue, 5 Feb 2013 01:34:24 +0000 (UTC) (envelope-from gjb@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 1A827DBC; Tue, 5 Feb 2013 01:34: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 r151YNUk070548; Tue, 5 Feb 2013 01:34:23 GMT (envelope-from gjb@svn.freebsd.org) Received: (from gjb@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r151YNAW070547; Tue, 5 Feb 2013 01:34:23 GMT (envelope-from gjb@svn.freebsd.org) Message-Id: <201302050134.r151YNAW070547@svn.freebsd.org> From: Glen Barber Date: Tue, 5 Feb 2013 01:34:23 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40888 - head/en_US.ISO8859-1/books/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-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 01:34:24 -0000 Author: gjb Date: Tue Feb 5 01:34:23 2013 New Revision: 40888 URL: http://svnweb.freebsd.org/changeset/doc/40888 Log: Fix build. Modified: head/en_US.ISO8859-1/books/handbook/boot/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/boot/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/boot/chapter.xml Mon Feb 4 22:21:54 2013 (r40887) +++ head/en_US.ISO8859-1/books/handbook/boot/chapter.xml Tue Feb 5 01:34:23 2013 (r40888) @@ -574,8 +574,8 @@ boot: To use larger images, up to the maximum resolution of 1024 by 768 pixels, load the VESA - module during system boot. For a custom kernel, include the + module during system boot. For a custom kernel, include the VESA kernel configuration option. Loading VESA support provides the ability to display a splash screen image that fills the From owner-svn-doc-head@FreeBSD.ORG Tue Feb 5 14:15:57 2013 Return-Path: Delivered-To: svn-doc-head@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 A422BF2B; Tue, 5 Feb 2013 14:15:57 +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 96A87B3C; Tue, 5 Feb 2013 14:15:57 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r15EFvnV004793; Tue, 5 Feb 2013 14:15:57 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r15EFvIY004792; Tue, 5 Feb 2013 14:15:57 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201302051415.r15EFvIY004792@svn.freebsd.org> From: Eitan Adler Date: Tue, 5 Feb 2013 14:15:57 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40894 - head/en_US.ISO8859-1/articles/committers-guide X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 14:15:57 -0000 Author: eadler Date: Tue Feb 5 14:15:57 2013 New Revision: 40894 URL: http://svnweb.freebsd.org/changeset/doc/40894 Log: Access to cvsup-master is not very important anymore. Reviewed by: doc (remko, gavin, crees) Approved by: bcr (mentor) Modified: head/en_US.ISO8859-1/articles/committers-guide/article.xml Modified: head/en_US.ISO8859-1/articles/committers-guide/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/committers-guide/article.xml Tue Feb 5 10:11:29 2013 (r40893) +++ head/en_US.ISO8859-1/articles/committers-guide/article.xml Tue Feb 5 14:15:57 2013 (r40894) @@ -4159,24 +4159,6 @@ bak/packages packages from last complet there are at least some perks: - - - Direct access to cvsup-master - - - As a committer, you may apply to &a.kuriyama; for direct access - to cvsup-master.FreeBSD.org, - providing the public key output from cvpasswd - yourusername@FreeBSD.org - freefall.FreeBSD.org. Please note: you must - specify freefall.FreeBSD.org on the - cvpasswd command line even though the - actual server is cvsup-master. Access to - cvsup-master should not be overused as it is - a busy machine. - - - Free 4-CD and DVD Sets From owner-svn-doc-head@FreeBSD.ORG Tue Feb 5 19:44:24 2013 Return-Path: Delivered-To: svn-doc-head@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 F00B68BE; Tue, 5 Feb 2013 19:44:24 +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 D855B2D6; Tue, 5 Feb 2013 19:44: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 r15JiO7w006698; Tue, 5 Feb 2013 19:44:24 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r15JiOUR006697; Tue, 5 Feb 2013 19:44:24 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201302051944.r15JiOUR006697@svn.freebsd.org> From: Dru Lavigne Date: Tue, 5 Feb 2013 19:44:24 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40897 - head/en_US.ISO8859-1/books/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-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 19:44:25 -0000 Author: dru Date: Tue Feb 5 19:44:24 2013 New Revision: 40897 URL: http://svnweb.freebsd.org/changeset/doc/40897 Log: Fix incorrect "Win" value noticed by wblock. Approved by: bcr (mentor) Modified: head/en_US.ISO8859-1/books/handbook/boot/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/boot/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/boot/chapter.xml Tue Feb 5 17:24:39 2013 (r40896) +++ head/en_US.ISO8859-1/books/handbook/boot/chapter.xml Tue Feb 5 19:44:24 2013 (r40897) @@ -180,7 +180,7 @@ <filename>boot0</filename> Screenshot - F1 Windows + F1 Win F2 FreeBSD Default: F2 From owner-svn-doc-head@FreeBSD.ORG Wed Feb 6 10:04:39 2013 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9A1FE3B8; Wed, 6 Feb 2013 10:04:39 +0000 (UTC) (envelope-from culot@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 8CC7FE34; Wed, 6 Feb 2013 10:04: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 r16A4dl8071806; Wed, 6 Feb 2013 10:04:39 GMT (envelope-from culot@svn.freebsd.org) Received: (from culot@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r16A4dgN071805; Wed, 6 Feb 2013 10:04:39 GMT (envelope-from culot@svn.freebsd.org) Message-Id: <201302061004.r16A4dgN071805@svn.freebsd.org> From: Frederic Culot Date: Wed, 6 Feb 2013 10:04:39 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40898 - head/en_US.ISO8859-1/articles/contributors X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 10:04:39 -0000 Author: culot (ports committer) Date: Wed Feb 6 10:04:38 2013 New Revision: 40898 URL: http://svnweb.freebsd.org/changeset/doc/40898 Log: Add Michael Sanders for textproc/topic. PR: ports/175807 Modified: head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Modified: head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml ============================================================================== --- head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Tue Feb 5 19:44:24 2013 (r40897) +++ head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Wed Feb 6 10:04:38 2013 (r40898) @@ -6835,6 +6835,11 @@ + Michael Sanders + mike@topcat.hypermart.net + + + Michael Sardo jaeger16@yahoo.com From owner-svn-doc-head@FreeBSD.ORG Wed Feb 6 22:11:22 2013 Return-Path: Delivered-To: svn-doc-head@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 4659A268; Wed, 6 Feb 2013 22:11: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 2E7A0E85; Wed, 6 Feb 2013 22:11: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 r16MBM6v085343; Wed, 6 Feb 2013 22:11:22 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r16MBM77085341; Wed, 6 Feb 2013 22:11:22 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201302062211.r16MBM77085341@svn.freebsd.org> From: Eitan Adler Date: Wed, 6 Feb 2013 22:11:22 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40899 - head/share/xml X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2013 22:11:22 -0000 Author: eadler Date: Wed Feb 6 22:11:21 2013 New Revision: 40899 URL: http://svnweb.freebsd.org/changeset/doc/40899 Log: Remove broken links Approved by: bcr (mentor) Modified: head/share/xml/mirrors.xml Modified: head/share/xml/mirrors.xml ============================================================================== --- head/share/xml/mirrors.xml Wed Feb 6 10:04:38 2013 (r40898) +++ head/share/xml/mirrors.xml Wed Feb 6 22:11:21 2013 (r40899) @@ -1609,7 +1609,6 @@ ftp2.se.FreeBSD.org ftp://ftp2.se.FreeBSD.org/pub/FreeBSD/ - http://ftp2.se.FreeBSD.org/ rsync://ftp2.se.FreeBSD.org/ @@ -2112,8 +2111,7 @@ ftp9.us.FreeBSD.org - ftp://ftp9.us.FreeBSD.org/pub/FreeBSD/ - http://ftp9.us.FreeBSD.org/pub/os/FreeBSD/ + http://ftp9.us.FreeBSD.org/pub/FreeBSD/ From owner-svn-doc-head@FreeBSD.ORG Thu Feb 7 10:31:39 2013 Return-Path: Delivered-To: svn-doc-head@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 F1C85CDD; Thu, 7 Feb 2013 10:31:38 +0000 (UTC) (envelope-from keramida@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 E420B338; Thu, 7 Feb 2013 10:31: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 r17AVcFd008868; Thu, 7 Feb 2013 10:31:38 GMT (envelope-from keramida@svn.freebsd.org) Received: (from keramida@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r17AVcg5008867; Thu, 7 Feb 2013 10:31:38 GMT (envelope-from keramida@svn.freebsd.org) Message-Id: <201302071031.r17AVcg5008867@svn.freebsd.org> From: Giorgos Keramidas Date: Thu, 7 Feb 2013 10:31:38 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40900 - head/en_US.ISO8859-1/books/handbook/jails X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2013 10:31:39 -0000 Author: keramida Date: Thu Feb 7 10:31:38 2013 New Revision: 40900 URL: http://svnweb.freebsd.org/changeset/doc/40900 Log: Mention sysutils/qjail too as a jail management framework. It's a bit more advanced than ezjail, so it's worth pointing users to that too. PR: docs/175907 Submitted by: Joe Barbish Approved by: remko Modified: head/en_US.ISO8859-1/books/handbook/jails/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/jails/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/jails/chapter.xml Wed Feb 6 22:11:21 2013 (r40899) +++ head/en_US.ISO8859-1/books/handbook/jails/chapter.xml Thu Feb 7 10:31:38 2013 (r40900) @@ -556,6 +556,7 @@ jail_www_devf usage of its features. If the presented steps below look too complicated, it is advised to take a look at a simpler system such as sysutils/qjail or sysutils/ezjail, which provides an easier method of administering &os; jails and is not as sophisticated as this setup. From owner-svn-doc-head@FreeBSD.ORG Thu Feb 7 12:50:08 2013 Return-Path: Delivered-To: svn-doc-head@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 248FCA1F; Thu, 7 Feb 2013 12:50:08 +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 13069B65; Thu, 7 Feb 2013 12:50: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 r17Co7d1049727; Thu, 7 Feb 2013 12:50:07 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r17Co7Tk049726; Thu, 7 Feb 2013 12:50:07 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201302071250.r17Co7Tk049726@svn.freebsd.org> From: Eitan Adler Date: Thu, 7 Feb 2013 12:50:07 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40901 - head/en_US.ISO8859-1/htdocs X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2013 12:50:08 -0000 Author: eadler Date: Thu Feb 7 12:50:07 2013 New Revision: 40901 URL: http://svnweb.freebsd.org/changeset/doc/40901 Log: Public Relations and Corporate Liaison appear not to exist, and are certainly not listed on the linked page. Approved by: jkois (mentor) Modified: head/en_US.ISO8859-1/htdocs/mailto.xml Modified: head/en_US.ISO8859-1/htdocs/mailto.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/mailto.xml Thu Feb 7 10:31:38 2013 (r40900) +++ head/en_US.ISO8859-1/htdocs/mailto.xml Thu Feb 7 12:50:07 2013 (r40901) @@ -41,7 +41,7 @@

Who Is Responsible for What

-

Public Relations & Corporate Liaison, Security Officer, +

Marketing, Bugmeister, Security Officer, Postmaster, Webmaster etc.

From owner-svn-doc-head@FreeBSD.ORG Thu Feb 7 13:52:42 2013 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 38E8A216; Thu, 7 Feb 2013 13:52:42 +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 1CAEEF87; Thu, 7 Feb 2013 13:52:42 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r17DqfJF069924; Thu, 7 Feb 2013 13:52:41 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r17Dqfum069923; Thu, 7 Feb 2013 13:52:41 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201302071352.r17Dqfum069923@svn.freebsd.org> From: Eitan Adler Date: Thu, 7 Feb 2013 13:52:41 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40902 - 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-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2013 13:52:42 -0000 Author: eadler Date: Thu Feb 7 13:52:41 2013 New Revision: 40902 URL: http://svnweb.freebsd.org/changeset/doc/40902 Log: Update and clarify the freebsd-mail-bounces question (why mail to freebsd.org bounces) to reflect reality. Reviewed by: postmaster (dhw) Discussed on: -doc 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 Thu Feb 7 12:50:07 2013 (r40901) +++ head/en_US.ISO8859-1/books/faq/book.xml Thu Feb 7 13:52:41 2013 (r40902) @@ -7643,69 +7643,53 @@ hint.sio.7.irq="12" The FreeBSD.org mail - system implements some of the stricter - Postfix checks on incoming mail - and rejects mail that is either misconfigured or is - potential spam. Your mail might bounce for one of the - following reasons: + system implements some + Postfix checks on incoming mail + and rejects mail that is either from misconfigured relays or + otherwise appears likely to be spam. Some of the + specific requirements are: - The email is being sent from a known spam domain or - IP block. - - The &os; mail servers reject email from known spam - sources. If you have service through a company or - domain who generates or relays spam, please switch to a - service provider who does not. + The IP address of the SMTP client must + "reverse-resolve" to a forward + confirmed hostname. - The body of the email only contains HTML. - - Mail should be sent in plain text only. Please - configure your mail user agent to send plain - text. + The fully-qualified hostname given in the + SMTP conversation (either HELO or EHLO) must resolve + to the IP address of the client. + - - The mailer at FreeBSD.org cannot resolve - the IP address of the connecting host back to a - symbolic name. - - Working reverse DNS is a standard requirement for - accepting mail from a host. Set up reverse DNS for your - mail server's IP address. Many home services (DSL, - cable, dialup, etc.) will not give you this option. In - this case, relay your email through your service - provider's mail server. - + Other advice to help your mail reach its destination + include: + - The hostname given in the EHLO/HELO part of the SMTP - exchange cannot be resolved to an IP address. - - A fully qualified, resolvable host name is necessary - in this part of the SMTP dialogue before mail will be - accepted. If you do not have a host name that is - registered in the DNS, then you should use your service - provider's mail server to relay your mail. + Mail should be sent in plain text, and messages + sent to mailing lists should generally be no more than + 200KB in length. - Your message had a message ID ending with the string - localhost. - - Some mail user agents generate bad message IDs which - will not be accepted. You will need to persuade your mail - user agent to generate a valid message ID or else - configure your mail transfer agent to rewrite - them. + Avoid excessive cross posting. Choose + one mailing list which seems most + relevant and send it there. - - + + If you still have trouble with email infrastructure at + FreeBSD.org send a note + with the details to + postmaster@freebsd.org; Include a + date/time interval so that logs may be reviewed — + and note that we only keep one week's worth of mail logs. + (Be sure to specify the time zone or offset from + UTC.) + + From owner-svn-doc-head@FreeBSD.ORG Thu Feb 7 15:02:31 2013 Return-Path: Delivered-To: svn-doc-head@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 E3CA1165; Thu, 7 Feb 2013 15:02:31 +0000 (UTC) (envelope-from achim@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 D53C462A; Thu, 7 Feb 2013 15:02: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 r17F2V3s093652; Thu, 7 Feb 2013 15:02:31 GMT (envelope-from achim@svn.freebsd.org) Received: (from achim@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r17F2USF093642; Thu, 7 Feb 2013 15:02:30 GMT (envelope-from achim@svn.freebsd.org) Message-Id: <201302071502.r17F2USF093642@svn.freebsd.org> From: Achim Leubner Date: Thu, 7 Feb 2013 15:02:30 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40903 - 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-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2013 15:02:32 -0000 Author: achim (src committer) Date: Thu Feb 7 15:02:30 2013 New Revision: 40903 URL: http://svnweb.freebsd.org/changeset/doc/40903 Log: - Add myself to authors.ent, developers.ent - Add myself to contrib.committers.xml - Add my PGP public key - Add my news.xml entry Approved by: emaste (co-mentor) Added: head/share/pgpkeys/achim.key (contents, props changed) Modified: 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.committers.xml ============================================================================== --- head/en_US.ISO8859-1/articles/contributors/contrib.committers.xml Thu Feb 7 13:52:41 2013 (r40902) +++ head/en_US.ISO8859-1/articles/contributors/contrib.committers.xml Thu Feb 7 15:02:30 2013 (r40903) @@ -820,6 +820,10 @@ + &a.achim; + + + &a.truckman; Added: head/share/pgpkeys/achim.key ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/share/pgpkeys/achim.key Thu Feb 7 15:02:30 2013 (r40903) @@ -0,0 +1,41 @@ + + + +sub 2048R/E275EF01 2013-01-22 +]]> + Modified: head/share/pgpkeys/pgpkeys-developers.xml ============================================================================== --- head/share/pgpkeys/pgpkeys-developers.xml Thu Feb 7 13:52:41 2013 (r40902) +++ head/share/pgpkeys/pgpkeys-developers.xml Thu Feb 7 15:02:30 2013 (r40903) @@ -991,6 +991,11 @@ &pgpkey.lesi; + + &a.achim; + &pgpkey.achim; + + &a.cel; &pgpkey.cel; Modified: head/share/pgpkeys/pgpkeys.ent ============================================================================== --- head/share/pgpkeys/pgpkeys.ent Thu Feb 7 13:52:41 2013 (r40902) +++ head/share/pgpkeys/pgpkeys.ent Thu Feb 7 15:02:30 2013 (r40903) @@ -3,6 +3,7 @@ + Modified: head/share/xml/authors.ent ============================================================================== --- head/share/xml/authors.ent Thu Feb 7 13:52:41 2013 (r40902) +++ head/share/xml/authors.ent Thu Feb 7 15:02:30 2013 (r40903) @@ -22,6 +22,8 @@ ache@FreeBSD.org"> +achim@FreeBSD.org"> + acm@FreeBSD.org"> adam@FreeBSD.org"> Modified: head/share/xml/developers.ent ============================================================================== --- head/share/xml/developers.ent Thu Feb 7 13:52:41 2013 (r40902) +++ head/share/xml/developers.ent Thu Feb 7 15:02:30 2013 (r40903) @@ -14,6 +14,7 @@ $FreeBSD$ + Modified: head/share/xml/news.xml ============================================================================== --- head/share/xml/news.xml Thu Feb 7 13:52:41 2013 (r40902) +++ head/share/xml/news.xml Thu Feb 7 15:02:30 2013 (r40903) @@ -34,6 +34,15 @@ 1 + 23 + +

New committer: + Achim Leubner (src)

+ + + + + 22

New committer: From owner-svn-doc-head@FreeBSD.ORG Thu Feb 7 15:05:38 2013 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 0FECB593; Thu, 7 Feb 2013 15:05: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 01ED466D; Thu, 7 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 r17F5bf0094278; Thu, 7 Feb 2013 15:05:37 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r17F5bYc094277; Thu, 7 Feb 2013 15:05:37 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201302071505.r17F5bYc094277@svn.freebsd.org> From: Dru Lavigne Date: Thu, 7 Feb 2013 15:05:37 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40904 - head/en_US.ISO8859-1/books/handbook/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-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2013 15:05:38 -0000 Author: dru Date: Thu Feb 7 15:05:37 2013 New Revision: 40904 URL: http://svnweb.freebsd.org/changeset/doc/40904 Log: This patch addresses the following: - removes etc. and i.e. - fixes some title capitalization - fixes incorrect grammar and overuse of ; - fixes verb tense from future to active - fixes redundancy - general rewording to make a densely written dense subject slightly less dense - link added for trustedbsd website - spell out of acronyms introduced on first instance in section and used as acronym for all other instances - remove reference to trustedbsd mailing lists as these have only seen spam posts in past 6 years - reference to SEBSD was removed as does not exist - reference to deprecated lomac confusion removed - fix varname tags - note added that as of 8.x, MAC is in GENERIC Approved by: bcr (mentor) Modified: head/en_US.ISO8859-1/books/handbook/mac/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/mac/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/mac/chapter.xml Thu Feb 7 15:02:30 2013 (r40903) +++ head/en_US.ISO8859-1/books/handbook/mac/chapter.xml Thu Feb 7 15:05:37 2013 (r40904) @@ -27,44 +27,42 @@ &os; 5.X introduced new security extensions from the - TrustedBSD project based on the &posix;.1e draft. Two of the + TrustedBSD + Project based on the &posix;.1e draft. Two of the most significant new security mechanisms are file system Access Control Lists (ACLs) and Mandatory Access - Control (MAC) facilities. Mandatory Access - Control allows new access control modules to be loaded, - implementing new security policies. Some provide protections - of a narrow subset of the system, hardening a particular - service. Others provide comprehensive labeled security across - all subjects and objects. The mandatory part of the definition - comes from the fact that the enforcement of the controls is - done by administrators and the system, and is not left up to - the discretion of users as is done with discretionary access - control (DAC, the standard file and System - V IPC permissions on &os;). - - This chapter will focus on the - Mandatory Access Control Framework (MAC - Framework), and a set of pluggable security policy modules - enabling various security mechanisms. + Control (MAC) facilities. MAC allows new + access control modules to be loaded, implementing new security + policies. Some modules provide protections for a narrow subset + of the system, hardening a particular service. Others provide + comprehensive labeled security across all subjects and objects. + The mandatory part of the definition indicates that enforcement + of controls is performed by administrators and the operating + system. This is in contrast to the default security mechanism + of Discretionary Access Control (DAC where + enforcement is left to the discretion of users. + + This chapter focuses on the MAC framework + and the set of pluggable security policy modules &os; provides + for enabling various security mechanisms. After reading this chapter, you will know: - What MAC security policy modules - are currently included in &os; and their associated - mechanisms. + Which MAC security policy modules + are included in &os; and their associated mechanisms. - What MAC security policy modules - implement as well as the difference between a labeled and - non-labeled policy. + The capabilities of MAC security + policy modules as well as the difference between a labeled + and non-labeled policy. - How to efficiently configure a system to use - the MAC framework. + How to efficiently configure a system to use the + MAC framework. @@ -74,8 +72,7 @@ How to implement a more secure environment using the - MAC framework and the examples - shown. + MAC framework. @@ -94,36 +91,27 @@ - Be familiar with - the basics of kernel configuration/compilation - (). - - - Have some familiarity with security and how it pertains to &os; (). - The improper use of the - information contained herein may cause loss of system access, - aggravation of users, or inability to access the features - provided by X11. More importantly, MAC - should not be relied upon to completely secure a system. The - MAC framework only augments existing - security policy; without sound security practices and - regular security checks, the system will never be completely - secure. - - It should also be noted that the examples contained - within this chapter are just that, examples. It is not - recommended that these particular settings be rolled out - on a production system. Implementing the various security - policy modules takes a good deal of thought and testing. One - who does not fully understand exactly how everything works - may find him or herself going back through the entire system - and reconfiguring many files or directories. + Improper MAC configuration may cause + loss of system access, aggravation of users, or inability to + access the features provided by + Xorg. More importantly, + MAC should not be relied upon to completely + secure a system. The MAC framework only + augments an existing security policy. Without sound security + practices and regular security checks, the system will never + be completely secure. + + The examples contained within this chapter are for + demonstration purposes and the example settings should + not be implemented on a production + system. Implementing any security policy takes a good deal of + understanding, proper design, and thorough testing. @@ -135,10 +123,10 @@ modules will not be covered. A number of security policy modules included with the MAC framework have specific characteristics which are provided for both - testing and new module development. These include the + testing and new module development. These include &man.mac.test.4;, &man.mac.stub.4; and &man.mac.none.4;. For more information on these security policy modules and - the various mechanisms they provide, please review the manual + the various mechanisms they provide, refer to their manual pages. @@ -147,127 +135,117 @@ Key Terms in This Chapter Before reading this chapter, a few key terms must be - explained. This will hopefully clear up any confusion that - may occur and avoid the abrupt introduction of new terms - and information. + explained: - compartment: A compartment is a - set of programs and data to be partitioned or separated, - where users are given explicit access to specific components - of a system. Also, a compartment represents a grouping, - such as a work group, department, project, or topic. Using - compartments, it is possible to implement a need-to-know - security policy. + compartment: a set of programs and + data to be partitioned or separated, where users are given + explicit access to specific component of a system. A + compartment represents a grouping, such as a work group, + department, project, or topic. Compartments make it + possible to implement a need-to-know-basis security + policy. - high water mark: A high water mark - policy is one which permits the raising of security levels - for the purpose of accessing higher level information. In - most cases, the original level is restored after the process + high-watermark: this type of + policy permits the raising of security levels for the + purpose of accessing higher level information. In most + cases, the original level is restored after the process is complete. Currently, the &os; MAC - framework does not have a policy for this, but the - definition is included for completeness. + framework does not include this type of policy. - integrity: Integrity, as a key - concept, is the level of trust which can be placed on data. - As the integrity of the data is elevated, so does the - ability to trust that data. + integrity: the level of trust which + can be placed on data. As the integrity of the data is + elevated, so does the ability to trust that data. - label: A label is a security - attribute which can be applied to files, directories, or - other items in the system. It could be considered a - confidentiality stamp; when a label is placed on a file it - describes the security properties for that specific - file and will only permit access by files, users, resources, - etc. with a similar security setting. The meaning and - interpretation of label values depends on the policy - configuration: while some policies might treat a label as - representing the integrity or secrecy of an object, other - policies might use labels to hold rules for access. + label: a security attribute which + can be applied to files, directories, or other items in the + system. It could be considered a confidentiality stamp. + When a label is placed on a file, it describes the security + properties of that file and will only permit access by + files, users, and resources with a similar security setting. + The meaning and interpretation of label values depends on + the policy configuration. Some policies treat a label as + representing the integrity or secrecy of an object while + other policies might use labels to hold rules for + access. - level: The increased or decreased + level: the increased or decreased setting of a security attribute. As the level increases, its security is considered to elevate as well. - low water mark: A low water mark - policy is one which permits lowering of the security levels - for the purpose of accessing information which is less - secure. In most cases, the original security level of the - user is restored after the process is complete. The only - security policy module in &os; to use this is - &man.mac.lomac.4;. + low-watermark: this type of + policy permits lowering security levels for the purpose of + accessing information which is less secure. In most cases, + the original security level of the user is restored after + the process is complete. The only security policy module in + &os; to use this is &man.mac.lomac.4;. - multilabel: The - property is a file system option - which can be set in single user mode using the - &man.tunefs.8; utility, during the boot operation - using the &man.fstab.5; file, or during the creation of - a new file system. This option will permit an administrator - to apply different MAC labels on - different objects. This option only applies to security - policy modules which support labeling. + multilabel: this property is a file + system option which can be set in single user mode using + &man.tunefs.8;, during boot using &man.fstab.5;, or during + the creation of a new file system. This option permits + an administrator to apply different MAC + labels on different objects. This option only applies to + security policy modules which support labeling. - object: An object or system - object is an entity through which information flows - under the direction of a subject. - This includes directories, files, fields, screens, - keyboards, memory, magnetic storage, printers or any other - data storage/moving device. Basically, an object is a data - container or a system resource; access to an - object effectively means access to the - data. + object: an entity through which + information flows under the direction of a + subject. This includes directories, + files, fields, screens, keyboards, memory, magnetic storage, + printers or any other data storage or moving device. An + object is a data container or a system resource. Access to + an object effectively means access to + its data. - policy: A collection of rules + policy: a collection of rules which defines how objectives are to be achieved. A policy usually documents how certain - items are to be handled. This chapter will - consider the term policy in this - context as a security policy; i.e. - a collection of rules which will control the flow of data - and information and define whom will have access to that - data and information. + items are to be handled. This chapter considers the term + policy to be a security + policy, or a collection of rules which controls + the flow of data and information and defines who has access + to that data and information. - sensitivity: Usually used when - discussing MLS. A sensitivity level is - a term used to describe how important or secret the data + sensitivity: usually used when + discussing Multilevel Security MLS. A + sensitivity level describes how important or secret the data should be. As the sensitivity level increases, so does the - importance of the secrecy, or confidentiality of the + importance of the secrecy, or confidentiality, of the data. - single label: A single label is - when the entire file system uses one label to - enforce access control over the flow of data. When a file - system has this set, which is any time when the - option is not set, all - files will conform to the same label setting. + single label: a policy where the + entire file system uses one label to enforce access control + over the flow of data. Whenever + is not set, all files will conform to the same label + setting. - subject: a subject is any - active entity that causes information to flow between - objects; e.g., a user, user process, - system process, etc. On &os;, this is almost always a + subject: any active entity that + causes information to flow between + objects such as a user, user process, + or system process. On &os;, this is almost always a thread acting in a process on behalf of a user. @@ -280,99 +258,71 @@ MAC framework augments the security of the system as a whole. The various security policy modules provided by the MAC framework could be used - to protect the network and file systems, block users from - accessing certain ports and sockets, and more. Perhaps the - best use of the policy modules is to blend them together, by - loading several security policy modules at a time for a - multi-layered security environment. In a multi-layered security - environment, multiple policy modules are in effect to keep - security in check. This is different to a hardening policy, - which typically hardens elements of a system that is used only - for specific purposes. The only downside is administrative - overhead in cases of multiple file system labels, setting - network access control user by user, etc. - - These downsides are minimal when compared to the lasting - effect of the framework; for instance, the ability to pick - and choose which policies are required for a specific - configuration keeps performance overhead down. The reduction - of support for unneeded policies can increase the overall - performance of the system as well as offer flexibility of - choice. A good implementation would consider the overall - security requirements and effectively implement the various - security policy modules offered by the framework. - - Thus a system utilizing MAC features - should at least guarantee that a user will not be permitted - to change security attributes at will; all user utilities, - programs and scripts must work within the constraints of - the access rules provided by the selected security policy - modules; and that total control of the MAC - access rules are in the hands of the system - administrator. - - It is the sole duty of the system administrator to - carefully select the correct security policy modules. Some - environments may need to limit access control over the network; - in these cases, the &man.mac.portacl.4;, &man.mac.ifoff.4; and - even &man.mac.biba.4; policy modules might make good starting - points. In other cases, strict confidentiality of file system - objects might be required. Policy modules such as - &man.mac.bsdextended.4; and &man.mac.mls.4; exist for this - purpose. + to protect the network and file systems or to block users from + accessing certain ports and sockets. Perhaps the best use of + the policy modules is to load several security policy modules at + a time in order to provide a MLS environment. + This approach differs from a hardening policy, which typically + hardens elements of a system which are used only for specific + purposes. The downside to MLS is increased + administrative overhead. + + The overhead is minimal when compared to the lasting effect + of a framework which provides the ability to pick and choose + which policies are required for a specific configuration and + which keeps performance overhead down. The reduction of support + for unneeded policies can increase the overall performance of + the system as well as offer flexibility of choice. A good + implementation would consider the overall security requirements + and effectively implement the various security policy modules + offered by the framework. + + A system utilizing MAC guarantees that a + user will not be permitted to change security attributes at + will. All user utilities, programs, and scripts must work + within the constraints of the access rules provided by the + selected security policy modules and total control of the + MAC access rules are in the hands of the + system administrator. + + It is the duty of the system administrator to + carefully select the correct security policy modules. For an + environment that needs to limit access control over the network, + the &man.mac.portacl.4;, &man.mac.ifoff.4;, and &man.mac.biba.4; + policy modules make good starting points. For an environment + where strict confidentiality of file system objects is required, + consider the &man.mac.bsdextended.4; and &man.mac.mls.4; policy + modules. Policy decisions could be made based on network - configuration. Perhaps only certain users should be permitted - access to facilities provided by &man.ssh.1; to access the - network or the Internet. The &man.mac.portacl.4; would be - the policy module of choice for these situations. But what - should be done in the case of file systems? Should all access - to certain directories be severed from other groups or specific - users? Or should we limit user or utility access to specific - files by setting certain objects as classified? - - In the file system case, access to objects might be - considered confidential to some users, but not to others. - For an example, a large development team might be broken - off into smaller groups of individuals. Developers in - project A might not be permitted to access objects written - by developers in project B. Yet they might need to access - objects created by developers in project C; that is quite a - situation indeed. Using the different security policy modules - provided by the MAC framework; users could - be divided into these groups and then given access to the - appropriate areas without fear of information - leakage. - - Thus, each security policy module has a unique way of - dealing with the overall security of a system. Module selection - should be based on a well thought out security policy. In many - cases, the overall policy may need to be revised and - reimplemented on the system. Understanding the different + configuration. If only certain users should be permitted + access to &man.ssh.1;, the &man.mac.portacl.4; policy module is + a good choice. In the case of file systems, access to objects + might be considered confidential to some users, but not to + others. As an example, a large development team might be + broken off into smaller projects where developers in project A + might not be permitted to access objects written by developers + in project B. Yet both projects might need to access objects + created by developers in project C. Using the different + security policy modules provided by the MAC + framework, users could be divided into these groups and then + given access to the appropriate objects. + + Each security policy module has a unique way of dealing with + the overall security of a system. Module selection should be + based on a well thought out security policy which may require + revision and reimplementation. Understanding the different security policy modules offered by the MAC framework will help administrators choose the best policies for their situations. - The default &os; kernel does not include the option for - the MAC framework; thus the following - kernel option must be added before trying any of the examples or - information in this chapter: - - options MAC - - And the kernel will require a rebuild and a - reinstall. - - While the various manual pages for MAC - policy modules state that they may be built into the kernel, - it is possible to lock the system out of - the network and more. Implementing MAC - is much like implementing a firewall, care must be taken - to prevent being completely locked out of the system. The - ability to revert back to a previous configuration should be - considered while the implementation of MAC - remotely should be done with extreme caution. + Implementing MAC is much like + implementing a firewall, care must be taken to prevent being + completely locked out of the system. The ability to revert + back to a previous configuration should be considered and the + implementation of MAC remotely should be + done with extreme caution. @@ -383,65 +333,55 @@ which may be applied to subjects and objects throughout the system. - When setting a label, the user must be able to comprehend - what it is, exactly, that is being done. The attributes - available on an object depend on the policy module loaded, and - that policy modules interpret their attributes in different - ways. If improperly configured due to lack of comprehension, - or the inability to understand the implications, the result - will be the unexpected and perhaps, undesired, behavior of the - system. + When setting a label, the administrator must be able to + comprehend what exactly is being done and understand any + implications in order to prevent unexpected or undesired + behavior of the system. The attributes available on an object + depend on the loaded policy module as policy modules interpret + their attributes in different ways. The security label on an object is used as a part of a security access control decision by a policy. With some - policies, the label by itself contains all information necessary - to make a decision; in other models, the labels may be processed - as part of a larger rule set, etc. - - For instance, setting the label of - biba/low on a file will represent a label - maintained by the Biba security policy module, with a value - of low. + policies, the label contains all of the information necessary + to make a decision. In other policies, the labels may be + processed as part of a larger rule set. For instance, setting + the label of biba/low on a file will + represent a label maintained by the Biba security policy module, + with a value of low. A few policy modules which support the labeling feature - in &os; offer three specific predefined labels. These - are the low, high, and equal labels. Although they enforce - access control in a different manner with each policy module, - you can be sure that the low label will be the lowest setting, - the equal label will set the subject or object to be disabled - or unaffected, and the high label will enforce the highest - setting available in the Biba and MLS + in &os; offer three specific predefined labels: low, high, and + equal. Such policy modules enforce access control in a + different manner with each policy module, where the low label is + the lowest setting, the equal label sets the subject or object + to be disabled or unaffected, and the high label enforces the + highest setting available in the Biba and MLS policy modules. Within single label file system environments, only one - label may be used on objects. This will enforce one set of + label may be used on objects. This label enforces one set of access permissions across the entire system and in many environments may be all that is required. There are a few cases where multiple labels may be set on objects or subjects - in the file system. For those cases, the - option may be passed to + in the file system by passing to &man.tunefs.8;. In the case of Biba and MLS, a numeric label may be set to indicate the precise level of hierarchical control. This numeric level is used to partition or sort - information into different groups of say, classification only + information into different groups of classification only permitting access to that group or a higher group level. - In most cases the administrator will only be setting up a - single label to use throughout the file system. - - Hey wait, this is similar to - DAC! I thought MAC gave - control strictly to the administrator. That - statement still holds true, to some extent as + In most cases, the administrator will set up a single label + to use throughout the file system. This is similar to + DAC to some extent as root is the one in control and who configures the policies so that users are placed in the appropriate categories/access levels. Alas, many policy modules can restrict the root user as well. Basic control over objects will then be released to the group, but root may revoke or modify the settings - at any time. This is the hierarchal/clearance model covered + at any time. This is the hierarchical/clearance model covered by policies such as Biba and MLS. @@ -453,32 +393,29 @@ configuration or the manipulation and verification of the configuration. - All configuration may be done by use of the - &man.setfmac.8; and &man.setpmac.8; utilities. - The setfmac command is used to set - MAC labels on system objects while the - setpmac command is used to set the labels - on system subjects. Observe: + All configuration may be done using &man.setfmac.8; and + &man.setpmac.8;. setfmac is used to set + MAC labels on system objects while + setpmac is used to set the labels on system + subjects. Observe: &prompt.root; setfmac biba/high test - If no errors occurred with the command above, a prompt - will be returned. The only time these commands are not - quiescent is when an error occurred; similarly to the - &man.chmod.1; and &man.chown.8; commands. In some cases this - error may be a Permission denied and - is usually obtained when the label is being set or modified - on an object which is restricted.Other conditions - may produce different failures. For instance, the file may - not be owned by the user attempting to relabel the object, - the object may not exist or may be read only. A mandatory - policy will not allow the process to relabel the file, maybe + If the configuration is successful, the prompt will be + returned without error. A common error is + Permission denied which usually occurs + when the label is being set or modified on an object which is + restricted.Other conditions may produce different + failures. For instance, the file may not be owned by the + user attempting to relabel the object, the object may not + exist, or the object may be read only. A mandatory policy + will not allow the process to relabel the file, maybe because of a property of the file, a property of the process, or a property of the proposed new label value. For - example: a user running at low integrity tries to change the + example, a user running at low integrity tries to change the label of a high integrity file. Or perhaps a user running at low integrity tries to change the label of a low - integrity file to a high integrity label. The + integrity file to a high integrity label. The system administrator may use the following commands to overcome this: @@ -488,18 +425,16 @@ &prompt.root; getfmac test test: biba/high - As we see above, setpmac - can be used to override the policy module's settings by - assigning a different label to the invoked process. The - getpmac utility is usually used with - currently running processes, such as - sendmail: although it takes a - process ID in place of a command the logic is extremely - similar. If users attempt to manipulate a file not in their - access, subject to the rules of the loaded policy modules, - the Operation not permitted error - will be displayed by the mac_set_link - function. + setpmac can be used to override the + policy module's settings by assigning a different label to the + invoked process. getpmac is usually used + with currently running processes, such as + sendmail. It takes a process ID in + place of a command. If users attempt to manipulate a file not + in their access, subject to the rules of the loaded policy + modules, the Operation not permitted + error will be displayed by the + mac_set_link function. Common Label Types @@ -507,15 +442,14 @@ test: biba/high For the &man.mac.biba.4;, &man.mac.mls.4; and &man.mac.lomac.4; policy modules, the ability to assign simple labels is provided. These take the form of high, - equal and low, what follows is a brief description of - what these labels provide: + equal, and low, where: The low label is considered the lowest label setting an object or subject may have. - Setting this on objects or subjects will block their - access to objects or subjects marked high. + Setting this on objects or subjects blocks their access + to objects or subjects marked high. @@ -531,66 +465,62 @@ test: biba/high With respect to each policy module, each of those - settings will instate a different information flow - directive. Reading the proper manual pages will further - explain the traits of these generic label + settings will establish a different information flow + directive. Refer to the manual pages of the module to + determine the traits of these generic label configurations. Advanced Label Configuration Numeric grade labels are used for - comparison:compartment+compartment; - thus the following: + comparison:compartment+compartment. + For example: biba/10:2+3+6(5:2+3-20:2+3+4+5+6) - May be interpreted as: - - Biba Policy Label/Grade + may be interpreted as Biba Policy + Label/Grade 10:Compartments 2, 3 and 6: (grade 5 ...) In this example, the first grade would be considered the effective grade with effective compartments, the second grade - is the low grade and the last one is the high grade. - In most configurations these settings will not be used; - indeed, they offered for more advanced - configurations. - - When applied to system objects, they will only have a - current grade/compartments as opposed to system subjects - as they reflect the range of available rights in the - system, and network interfaces, where they are used for - access control. + is the low grade, and the last one is the high grade. + In most configurations, these settings will not be used + as they are advanced configurations. + + System objects only have a current grade/compartment. + System subjects reflect the range of available rights in + the system, and network interfaces, where they are used + for access control. The grade and compartments in a subject and object - pair are used to construct a relationship referred to as + pair are used to construct a relationship known as dominance, in which a subject dominates an object, the object dominates the subject, neither dominates the other, or both dominate each other. The both dominate case occurs when the two labels are equal. Due to the information flow nature of - Biba, you have rights to a set of compartments, - need to know, that might correspond to - projects, but objects also have a set of compartments. - Users may have to subset their rights using - su or setpmac in - order to access objects in a compartment from which they - are not restricted. + Biba, a user has rights to a set of compartments that + might correspond to projects, but objects also have a set + of compartments. Users may have to subset their rights + using su or setpmac + in order to access objects in a compartment from which + they are not restricted. Users and Label Settings - Users themselves are required to have labels so that - their files and processes may properly interact with the - security policy defined on the system. This is - configured through the login.conf file - by use of login classes. Every policy module that uses - labels will implement the user class setting. + Users are required to have labels so that their files + and processes properly interact with the security policy + defined on the system. This is configured in + login.conf using login classes. Every + policy module that uses labels will implement the user class + setting. An example entry containing every policy module setting is displayed below: @@ -619,49 +549,49 @@ test: biba/high :ignoretime@:\ :label=partition/13,mls/5,biba/10(5-15),lomac/10[2]: - The label option is used to set the + To set the user class default label which will be enforced by - MAC. Users will never be permitted to - modify this value, thus it can be considered not optional - in the user case. In a real configuration, however, the - administrator will never wish to enable every policy module. - It is recommended that the rest of this chapter be reviewed - before any of this configuration is implemented. + MAC, use . Users + are never permitted to modify this value. In a real + configuration, however, the administrator would never enable + every policy module. It is recommended that the rest of + this chapter be reviewed before any configuration is + implemented. - Users may change their label after the initial login; - however, this change is subject constraints of the policy. - The example above tells the Biba policy that a process's - minimum integrity is 5, its maximum is 15, but the default - effective label is 10. The process will run at 10 until - it chooses to change label, perhaps due to the user using - the setpmac command, which will be constrained by Biba to - the range set at login. + Users may change their label after they login, subject + to the constraints of the policy. The example above tells + the Biba policy that a process's minimum integrity is 5, + its maximum is 15, and the default effective label is 10. + The process will run at 10 until it chooses to change + label, perhaps due to the user using &man.setpmac.8;, + which will be constrained by Biba to the configured + range. - In all cases, after a change to + After any change to login.conf, the login class capability - database must be rebuilt using cap_mkdb - and this will be reflected throughout every forthcoming - example or discussion. - - It is useful to note that many sites may have a - particularly large number of users requiring several - different user classes. In depth planning is required - as this may get extremely difficult to manage. + database must be rebuilt using + cap_mkdb. + + Many sites have a large number of users requiring + several different user classes. In depth planning is + required as this may get extremely difficult to + manage. Network Interfaces and Label Settings - Labels may also be set on network interfaces to help - control the flow of data across the network. In all cases - they function in the same way the policies function with - respect to objects. Users at high settings in - biba, for example, will not be permitted - to access network interfaces with a label of low. + Labels may be set on network interfaces to help + control the flow of data across the network. Policies + using network interface labels function in the same way that + policies function with respect to objects. Users at high + settings in biba, for example, will not + be permitted to access network interfaces with a label of + low. - The may be passed to + may be passed to ifconfig when setting the MAC label on network interfaces. For example: @@ -671,51 +601,44 @@ test: biba/high will set the MAC label of biba/equal on the &man.bge.4; interface. When using a setting similar to - biba/high(low-high) the entire label - should be quoted; otherwise an error will be + biba/high(low-high), the entire label + should be quoted to prevent an error from being returned. Each policy module which supports labeling has a tunable which may be used to disable the MAC label on network interfaces. Setting the label to will have a similar effect. Review - the output from sysctl, the policy manual - pages, or even the information found later in this chapter - for those tunables. + the output of sysctl, the policy manual + pages, and the information in this chapter for more + information on those tunables. Singlelabel or Multilabel? - By default the system will use the - option. But what does this - mean to the administrator? There are several differences - which, in their own right, offer pros and cons to the - flexibility in the systems security model. - - The only permits for one - label, for instance biba/high to be used - for each subject or object. It provides for lower - administration overhead but decreases the flexibility of - policies which support labeling. Many administrators may - want to use the option in - their security policy. - - The option will permit each - subject or object to have its own independent - MAC label in - place of the standard option - which will allow only one label throughout the partition. - The and - label options are only required for the policies which - implement the labeling feature, including the Biba, Lomac, - MLS and SEBSD - policies. - - In many cases, the may not - need to be set at all. Consider the following situation and - security model: + By default, the system will use + . For the administrator, there + are several differences which offer pros and cons to the + flexibility in the system's security model. + + A security policy which uses + only permits one label, such as biba/high, + to be used for each subject or object. This provides lower + administration overhead, but decreases the flexibility of + policies which support labeling. + + permits each subject or object + to have its own independent MAC label. + The decision to use or + is only required for the policies + which implement the labeling feature, including the Biba, + Lomac, and MLS policies. + + In many cases, may not be + needed. Consider the following situation and security + model: @@ -726,49 +649,41 @@ test: biba/high This machine only requires one label, biba/high, for everything in the - system. Here the file system would not require the - option as a single label - will always be in effect. + system. This file system would not require + as a single label will always + be in effect. But, this machine will be a web server and should have the web server run at biba/low - to prevent write up capabilities. The Biba policy and - how it works will be discussed later, so if the previous - comment was difficult to interpret just continue reading - and return. The server could use a separate partition - set at biba/low for most if not all - of its runtime state. Much is lacking from this example, - for instance the restrictions on data, configuration and - user settings; however, this is just a quick example to - prove the aforementioned point. + to prevent write up capabilities. The server could + use a separate partition set at + biba/low for most if not all + of its runtime state. If any of the non-labeling policies are to be used, - then the option would never - be required. These include the - seeotheruids, portacl - and partition policies. - - It should also be noted that using - with a partition and establishing - a security model based on - functionality could open the doors for higher administrative - overhead as everything in the file system would have a label. - This includes directories, files, and even device + would not be required. These + include the seeotheruids, + portacl and partition + policies. + + Using with a partition and + establishing a security model based on + functionality could increase + administrative overhead as everything in the file system has a + label. This includes directories, files, and even device nodes. The following command will set on the file systems to have multiple labels. This may only be - done in single user mode: + done in single user mode and is not a requirement for the swap *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-head@FreeBSD.ORG Thu Feb 7 15:09:55 2013 Return-Path: Delivered-To: svn-doc-head@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 98769AE4; Thu, 7 Feb 2013 15:09:55 +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 7F9126D6; Thu, 7 Feb 2013 15:09:55 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r17F9tQT095207; Thu, 7 Feb 2013 15:09:55 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r17F9tX4095206; Thu, 7 Feb 2013 15:09:55 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201302071509.r17F9tX4095206@svn.freebsd.org> From: Dru Lavigne Date: Thu, 7 Feb 2013 15:09:55 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40905 - 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-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2013 15:09:55 -0000 Author: dru Date: Thu Feb 7 15:09:55 2013 New Revision: 40905 URL: http://svnweb.freebsd.org/changeset/doc/40905 Log: This patch addresses the following: - fixes missing &os;, &linux; and incorrect tags - general rewording to replace "you" and address redundancy - removes deprecated apps: abacus, gimp-devel, guppi, konq-plugins and renames koffice to calligra - incorporates redundant summary into synopsis - fixes incorrect port/pkg names and adds localization notes where applicable - moves some to as they make more sense as subsections - rm openjdk compile as icedtea Makefile now does this for user - bumps up some pkg/port versions - adds some URLs to less known apps Approved by: bcr (mentor) 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 Thu Feb 7 15:05:37 2013 (r40904) +++ head/en_US.ISO8859-1/books/handbook/desktop/chapter.xml Thu Feb 7 15:09:55 2013 (r40905) @@ -20,84 +20,188 @@ Synopsis - FreeBSD can run a wide variety of desktop applications, such - as browsers and word processors. Most of these are available as - packages or can be automatically built from the Ports - Collection. Many new users expect to find these kinds of - applications on their desktop. This chapter will show you how - to install some popular desktop applications effortlessly, - either from their packages or from the Ports Collection. - - Note that when installing programs from the ports, they are - compiled from source. This can take a very long time, depending - on what you are compiling and the processing power of your - machine(s). If building from source takes a prohibitively long - amount of time for you, you can install most of the programs of - the Ports Collection from pre-built packages. - - As FreeBSD features Linux binary compatibility, many - applications originally developed for Linux are available for - your desktop. It is strongly recommended that you read - before installing any of the Linux - applications. Many of the ports using the Linux binary - compatibility start with linux-. Remember this - when you search for a particular port, for instance with - &man.whereis.1;. In the following text, it is assumed that you - have enabled Linux binary compatibility before installing any of - the Linux applications. + While &os; is popular as a server for its performance and + stability, it is also suited for day-to-day use as a desktop. + With over 24,000 applications available as packages or ports, it is easy to build a + customized desktop that runs a wide variety of desktop + applications. This chapter demonstrates how to install some + popular desktop applications effortlessly using packages or the + &os; Ports Collection. + + As &os; features &linux; binary + compatibility, many applications developed for &linux; + can be installed on a &os; desktop. Many of the ports using + &linux; binary compatibility start with linux-. + This chapter assumes that &linux; binary compatibility has been + enabled before any &linux; applications are installed. - Here are the categories covered by this chapter: + This chapter demonstrates how to install the following + desktop applications: - - - Browsers (such as Firefox, - Opera, - Konqueror, - Chromium) - + + + + + Type of Application + Application Name + Package Name + Ports Name + + - - Productivity (such as - KOffice, - AbiWord, - The GIMP, - Apache OpenOffice, - LibreOffice) - + - - Document Viewers (such as - &acrobat.reader;, - gv, - Xpdf, - GQview) - + + Browser + Firefox + firefox + www/firefox + - - Finance (such as - GnuCash, - Gnumeric, - Abacus) - - + + Browser + Opera + opera + www/opera + - Before reading this chapter, you should: + + Browser + Konqueror + kde4-baseapps + x11/kde4-baseapps + + + + Browser + Chromium + chromium + www/chromium + + + + Productivity + Calligra + calligra + editors/calligra + + + + Productivity + AbiWord + abiword + editors/abiword + + + + Productivity + The GIMP + gimp + graphics/gimp + + + + Productivity + Apache + OpenOffice + openoffice + editors/openoffice-3 + + + + Productivity + LibreOffice + libreoffice + editors/libreoffice + + + + Document Viewer + &acrobat.reader; + no package due to + license restriction + print/acroread9 + + + + Document Viewer + gv + gv + print/gv + + + + Document Viewer + Xpdf + xpdf + graphics/xpdf + + + + Document Viewer + GQview + gqview + graphics/gqview + + + + Finance + GnuCash + gnucash + finance/gnucash + + + + Finance + Gnumeric + gnumeric + math/gnumeric + + + + KMyMoney + kmymoney-kde4 + finance/kmymoney-kde4 + + + + + + Before reading this chapter, you should know how to: - Know how to install additional third-party software - (). + Install additional software using packages or + ports. - Know how to install additional Linux software - (). + Enable &linux; binary compatibility. - For information on how to get a multimedia environment, read - . If you want to set up and use - electronic mail, please refer to . + For information on how to configure a multimedia + environment, refer to . For + information on how to set up and use electronic mail, refer to + . @@ -108,26 +212,28 @@ web - FreeBSD does not come with a particular browser - pre-installed. Instead, the - www - directory of the Ports Collection contains a lot of browsers - ready to be installed. If you do not have time to compile - everything (this can take a very long time in some cases) many - of them are available as packages. - - KDE and - GNOME already provide HTML browsers. - Please refer to for more information on - how to set up these complete desktops. + &os; does not come with a pre-installed web browser. + Instead, the www + category of the Ports Collection contains many browsers which + can be installed as a package or compiled from the Ports + Collection. + + The KDE and + GNOME desktop environments include + their own HTML browser. Refer to + for more information on how to set up these complete + desktops. - If you are looking for light-weight browsers, you should - investigate the Ports Collection for + Some light-weight browsers include www/dillo2, - www/links, or + www/links, and www/w3m. - This section covers these applications: + This section demonstrates how to install the following + popular web browsers and indicates if the application is + resource-heavy, takes time to compile from ports, or has any + major dependencies. @@ -136,7 +242,7 @@ Application Name Resources Needed Installation from Ports - Major Dependencies + Notes @@ -145,30 +251,30 @@ Firefox medium heavy - Gtk+ + &os; and &linux; versions are + available Opera light light - FreeBSD and Linux versions available. The Linux - version depends on the Linux Binary Compatibility and - linux-openmotif. + &os; and &linux; versions are available Konqueror medium heavy - KDE Libraries + Requires KDE + libraries Chromium medium medium - Gtk+ + Requires Gtk+ @@ -182,65 +288,62 @@ Firefox is a modern, free, - open-source stable browser that is fully ported to &os;: it - features a very standards-compliant HTML display engine, - tabbed browsing, popup blocking, extensions, improved - security, and more. Firefox is - based on the Mozilla - codebase. + open source browser that is fully ported to &os;. It + features a standards-compliant HTML display engine, tabbed + browsing, popup blocking, extensions, improved security, and + more. Firefox is based on the + Mozilla codebase. - Install the package by typing: + Install the package of the latest release version of + Firefox by typing: &prompt.root; pkg_add -r firefox - This will install the latest release version of - Firefox, - if you want to run Firefox - Extended Support Release (ESR) version, use instead: + To instead install Firefox + Extended Support Release (ESR) version, use: &prompt.root; pkg_add -r firefox-esr - You can also use the Ports Collection if you - prefer to compile from source code: + Localized versions are available in www/firefox-i18n and www/firefox-esr-i18n. + + The Ports Collection can instead be used to compile + the desired version of firefox from + source code. This example builds www/firefox, where + firefox can be replaced with the ESR or + localized version to install. &prompt.root; cd /usr/ports/www/firefox &prompt.root; make install clean - For Firefox ESR, in the - previous command replace firefox with - firefox-esr. - - - + Firefox and &java; Plugin - In this section and in the next two sections, we assume - you have already installed - Firefox. + The following sections assume that + Firefox is already + installed. - Install OpenJDK 6 - through the Ports Collection by typing: - - &prompt.root; cd /usr/ports/java/openjdk6 -&prompt.root; make install clean - - Then install the - java/icedtea-web - port: + java/icedtea-web + provides a free software web browser plugin for running + Java applets. It can be installed as a package. To + alternately compile the port: &prompt.root; cd /usr/ports/java/icedtea-web &prompt.root; make install clean - Make sure you have kept the default configuration options - for both ports. + Keep the default configuration options when compiling the + port. - Start your browser, enter about:plugins - in the location bar and press Enter. A page - listing the installed plugins will be displayed; the - &java; plugin should be listed - there now. + Once installed, start firefox, + enter about:plugins in the location bar and + press Enter. A page listing the installed + plugins will be displayed. The + &java; plugin should be + listed. If the browser is unable to find the plugin, each user will have to run the following command and relaunch the @@ -248,9 +351,9 @@ &prompt.user; ln -s /usr/local/lib/IcedTeaPlugin.so \ $HOME/.mozilla/plugins/ - + - + Firefox and &adobe; &flash; Plugin @@ -258,93 +361,90 @@ Flash - The &adobe; &flash; plugin is not available for &os;. - However, a software layer (wrapper) for running the Linux - version of the plugin exists. This wrapper also supports - &adobe; &acrobat; plugin, &realplayer; plugin and more. + A native &adobe; &flash; plugin is not available for &os;. + However, a software layer (wrapper) for running the &linux; + version of the plugin exists. This wrapper also provides + support for other browser plugins such as &realplayer;. - According to the version of &os; you run various steps are - required: + The steps required to install and enable this plugin vary + by the &os; version: Under &os; 7.X - Install the - www/nspluginwrapper - port. This port requires Install the www/nspluginwrapper package + or port. This application requires emulators/linux_base-fc4 which is a large port. - The next step is to install the - www/linux-flashplugin9 - port. This will install &flash; 9.X, this version is - known to run correctly under &os; 7.X. + Next, install www/linux-flashplugin9. This + will install &flash; 9.X which is the version known to + run correctly under &os; 7.X. Under &os; 8.X or Newer - Install the - www/nspluginwrapper - port. This port requires Compile the www/nspluginwrapper port. + Due to licensing restrictions, a package is not available. + This port requires emulators/linux_base-f10 which is a large port. - The next step is to install &flash; 11.X from the - Next, compile the www/linux-f10-flashplugin11 - port. + port. Due to licensing restrictions, a package is not + available. - This version will require the following link to be - created: + This version of &flash; requires the following link to + be created: &prompt.root; ln -s /usr/local/lib/npapi/linux-f10-flashplugin/libflashplayer.so \ /usr/local/lib/browser_plugins/ - The Manually create /usr/local/lib/browser_plugins - directory will have to be created manually if it does not - exist on the system. + if it does not already exist on the system. - Once the right &flash; port, according to the &os; version - you run, - is installed, the plugin must be installed by each + Once the right &flash; port, according to the &os; + version, is installed, the plugin must be installed by each user with nspluginwrapper: &prompt.user; nspluginwrapper -v -a -i - Then, start your browser, enter - about:plugins in the location bar and press - Enter. - A list should appear with all the currently - available plugins. - + Start the browser, enter about:plugins + in the location bar and press Enter. A list + should appear with all the currently available plugins. + - + Firefox and Swfdec &flash; Plugin Swfdec is the library for decoding and rendering &flash; - animations. And Swfdec-Mozilla is a plugin for + animations. Swfdec-Mozilla is a plugin for Firefox browsers that uses the Swfdec library for playing SWF files. It is still in heavy development. - If you cannot or do not want to compile it, just install - the package from the network: + To install the package: &prompt.root; pkg_add -r swfdec-plugin - If the package is not available, you can compile and - install it from the Ports Collection: + If the package is not available, compile and install it + from the Ports Collection: &prompt.root; cd /usr/ports/www/swfdec-plugin &prompt.root; make install clean - Then, restart your browser for this plugin taking - effect. + Restart the browser for this plugin to take + effect. + @@ -354,48 +454,48 @@ Opera - Opera is a - full-featured and standards-compliant browser. It also - comes with a built-in mail and news reader, an IRC client, - an RSS/Atom feeds reader and much more. Despite this, - Opera is relatively lightweight and - very fast. It comes in two flavors: a native - FreeBSD version and a version that runs under Linux - emulation. - - To browse the Web with the FreeBSD version of - Opera, install the package: + Opera is a full-featured and + standards-compliant browser which is still lightweight and + fast. It comes with a built-in mail and news reader, an IRC + client, an RSS/Atom feeds reader, and more. It is available + as a native &os; version and as a version that runs under + &linux; emulation. + + This command installs the package of the &os; version of + Opera. Replace + opera with linux-opera + to instead install the &linux; version. &prompt.root; pkg_add -r opera - Some FTP sites do not have all the packages, but - Opera can still be obtained - through the Ports Collection by typing: + Alternately, install either version through the Ports + Collection. This example compiles the native version: &prompt.root; cd /usr/ports/www/opera &prompt.root; make install clean - To install the Linux version of - Opera, substitute + To install the &linux; version, substitute linux-opera in place of - opera in the example above. + opera. - The &adobe; &flash; plugin is not available for &os;. - However, a &linux; version of the plugin exists. To install - this version, the www/linux-f10-flashplugin11 port - has to be installed, then install the port www/opera-linuxplugins: + To install &adobe; &flash; plugin support, first compile + the www/linux-f10-flashplugin11 port, + as a package is not available due to licensing restrictions. + Then install either the www/opera-linuxplugins port + or package. This example compiles both from ports: &prompt.root; cd /usr/ports/www/linux-f10-flashplugin11 &prompt.root; make install clean &prompt.root; cd /usr/ports/www/opera-linuxplugins &prompt.root; make install clean - You can check the presence of the plugin: start your - browser, enter opera:plugins in the - location bar and press Enter. A list should - appear with all the currently available plugins. + Once installed, check the presence of the plugin by + starting the browser, entering + opera:plugins in the location bar and + pressing Enter. A list should appear with + all the currently available plugins. To add the &java; plugin, follow the instructions for @@ -409,32 +509,33 @@ Konqueror - Konqueror is part of - KDE but it can also be used outside - of KDE by installing - x11/kdebase3. - Konqueror is much more than a - browser, it is also a file manager and a multimedia + Konqueror is part of x11/kde4-baseapps. + Konqueror is more than a web + browser as it is also a file manager and a multimedia viewer. - There is also a set of plugins available for - Konqueror, available in - misc/konq-plugins. - Konqueror supports WebKit as - well as its own KHTML. WebKit is used by many modern browsers - including Chromium. To use WebKit with - Konqueror on &os;: + well as its own KHTML. WebKit is a rendering engine used by + many modern browsers including Chromium. To use WebKit with + Konqueror on &os;, install + the www/kwebkitpart package or + port. This example compiles the port: &prompt.root; cd /usr/ports/www/kwebkitpart &prompt.root; make install clean - Then in Konqueror, click - Settings, Configure Konqueror, - then Change KHTML to WebKit. + To enable WebKit within + Konqueror, click + Settings, Configure Konqueror. + In the General settings page, click the + drop-down menu next to Default web browser + engine and change KHTML to + WebKit. Konqueror also supports - &flash;; a How To + &flash;. A How To guide for getting &flash; support on Konqueror is available at . @@ -447,12 +548,12 @@ Chromium - Chromium is an open-source + Chromium is an open source browser project that aims to build a safer, faster, and more stable web browsing experience. Chromium features tabbed browsing, popup blocking, extensions, and much more. - Chromium is the open-source project + Chromium is the open source project upon which the Google Chrome web browser is based. Chromium can be installed as a @@ -467,34 +568,25 @@ &prompt.root; make install clean - Chromium is installed as - /usr/local/bin/chrome, not + The executable for Chromium + is /usr/local/bin/chrome, not /usr/local/bin/chromium. - - + Chromium and &java; Plugin - This section assumes Chromium - is already installed. + The following sections assume that + Chromium is already + installed. - Install OpenJDK 6 through - the Ports Collection by typing: + To install &java; plugin support, follow the instructions + in . - &prompt.root; cd /usr/ports/java/openjdk6 -&prompt.root; make install clean - - Next, install - java/icedtea-web from the - Ports Collection: - - &prompt.root; cd /usr/ports/java/icedtea-web -&prompt.root; make install clean - - Start Chromium, and enter + Once &java; support is installed, start + Chromium, and enter about:plugins in the address bar. IcedTea-Web should be listed as one of the installed plugins. @@ -506,24 +598,18 @@ &prompt.root; mkdir -p /usr/local/share/chromium/plugins &prompt.root; ln -s /usr/local/lib/IcedTeaPlugin.so \ /usr/local/share/chromium/plugins/ - - - - Chromium and &adobe; &flash; Plugin + - - This section assumes Chromium - is already installed. - + + Chromium and &adobe; &flash; Plugin - Configuring Chromium and - &adobe; &flash; is similar to the - instructions for - Firefox. For more detailed instructions on - installing &adobe; &flash; on &os;, please refer to that - section. No additional configuration should be necessary, - since Chromium is able to use some - plugins from other browsers. + Configuring Chromium and + &adobe; &flash; is similar to the + instructions for + Firefox. No additional configuration should be + necessary, since Chromium is able + to use some plugins from other browsers. + @@ -534,11 +620,14 @@ good office suite or a friendly word processor. While some desktop environments like KDE already provide an office suite, - there is no default productivity package. FreeBSD can provide - all that is needed, regardless of your desktop - environment. - - This section covers these applications: + there is no default productivity package. Several office + suites and word processors are available for &os;, regardless + of the installed desktop environment. + + This section demonstrates how to install the following + popular web browsers and indicates if the application is + resource-heavy, takes time to compile from ports, or has any + major dependencies. @@ -553,7 +642,7 @@ - KOffice + Calligra light heavy KDE @@ -579,7 +668,7 @@ OpenOffice heavy huge - &jdk;, + &jdk; and Mozilla @@ -597,42 +686,37 @@ - KOffice + Calligra - KOffice + Calligra office suite - KOffice + Calligra - The KDE community has provided its desktop environment - with an office suite which can be used outside - KDE. It includes the four standard + The KDE community provides its desktop environment with + an office suite which can be used outside of + KDE. + Calligra includes standard components that can be found in other office suites. - KWord is the word processor, - KSpread is the spreadsheet program, - KPresenter manages slide - presentations, and Kontour lets you - draw graphical documents. - - Before installing the latest - KOffice, make sure you have an - up-to-date version of KDE. - - To install KOffice for - KDE4 as a - package, issue the following command: - - &prompt.root; pkg_add -r koffice-kde4 - - If the package is not available, you can use the Ports - Collection. For instance, to install - KOffice for - KDE4, do: + Words is the word processor, + Sheets is the spreadsheet program, + Stage manages slide presentations, + and Karbon is used to draw + graphical documents. + + editors/calligra can be installed + as a package or a port. To install the package: + + &prompt.root; pkg_add -r calligra + + If the package is not available, use the Ports Collection + instead: - &prompt.root; cd /usr/ports/editors/koffice-kde4 + &prompt.root; cd /usr/ports/editors/calligra &prompt.root; make install clean @@ -647,21 +731,19 @@ processing program similar in look and feel to µsoft; Word. It is suitable for typing papers, letters, reports, memos, and so forth. It - is very fast, contains many features, and is very - user-friendly. + is fast, contains many features, and is user-friendly. AbiWord can import or export many file formats, including some proprietary ones like - µsoft;'s .doc. + µsoft; .doc. - AbiWord is available as a - package. You can install it by: + To install the AbiWord + package: &prompt.root; pkg_add -r abiword If the package is not available, it can be compiled from - the Ports Collection. The Ports Collection should be more - up to date. It can be done as follows: + the Ports Collection: &prompt.root; cd /usr/ports/editors/abiword &prompt.root; make install clean @@ -675,41 +757,29 @@ For image authoring or picture retouching, - The GIMP is a very sophisticated + The GIMP provides a sophisticated image manipulation program. It can be used as a simple paint program or as a quality photo retouching suite. It supports a - large number of plug-ins and features a scripting interface. + large number of plugins and features a scripting interface. The GIMP can read and write a wide - range of file formats. It supports interfaces with scanners + range of file formats and supports interfaces with scanners and tablets. - You can install the package by issuing this - command: + To install the package: &prompt.root; pkg_add -r gimp - If your FTP site does not have this package, you can use - the Ports Collection. The graphics - directory of the Ports Collection also contains - The Gimp Manual. Here is how to - get them installed: + Alternately, use the Ports Collection: &prompt.root; cd /usr/ports/graphics/gimp -&prompt.root; make install clean -&prompt.root; cd /usr/ports/graphics/gimp-manual-pdf &prompt.root; make install clean - - The graphics - directory of the Ports Collection holds the development - version of The GIMP in - graphics/gimp-devel. An - HTML version of The Gimp Manual - is available from graphics/gimp-manual-html. - + The graphics + category of the Ports Collection contains several + GIMP-related plugins, help + files, and user manuals. + @@ -727,105 +797,91 @@ - On 1 June 2011, Oracle Corporation donated the *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-head@FreeBSD.ORG Thu Feb 7 15:53:27 2013 Return-Path: Delivered-To: svn-doc-head@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 C85CEBB3; Thu, 7 Feb 2013 15:53:27 +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 B4D4F98D; Thu, 7 Feb 2013 15:53:27 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r17FrRIG010368; Thu, 7 Feb 2013 15:53:27 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r17FrR7r010367; Thu, 7 Feb 2013 15:53:27 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201302071553.r17FrR7r010367@svn.freebsd.org> From: Dru Lavigne Date: Thu, 7 Feb 2013 15:53:27 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40906 - head/en_US.ISO8859-1/books/handbook/disks X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2013 15:53:27 -0000 Author: dru Date: Thu Feb 7 15:53:27 2013 New Revision: 40906 URL: http://svnweb.freebsd.org/changeset/doc/40906 Log: This patch addresses the following: - fix &os;, , incorrect directory, varname, and devicename tags - general rewording/tightening to address "you" and redundancy - one comment was weirdly tagged and I couldn't figure out how to fix it so it was removed - a newfs example was modified as UFS2 is now the default Approved by: bcr (mentor) Modified: head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/disks/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Thu Feb 7 15:09:55 2013 (r40905) +++ head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Thu Feb 7 15:53:27 2013 (r40906) @@ -11,7 +11,7 @@ Synopsis - This chapter covers the use of disks in FreeBSD. This + This chapter covers the use of disks in &os;. This includes memory-backed disks, network-attached disks, standard SCSI/IDE storage devices, and devices using the USB interface. @@ -20,13 +20,13 @@ - The terminology FreeBSD uses to describe the - organization of data on a physical disk (partitions and - slices). + The terminology &os; uses to describe the organization + of data on a physical disk. - How to add additional hard disks to your system. + How to add additional hard disks to a &os; + system. @@ -48,7 +48,7 @@ - How to create and burn CDs and DVDs on FreeBSD. + How to create and burn CDs and DVDs on &os;. @@ -56,8 +56,8 @@ - How to use backup programs available under - FreeBSD. + How to use the backup programs available under + &os;. @@ -74,8 +74,8 @@ - Know how to configure and install a new FreeBSD kernel - (). + Know how to configure and + install a new &os; kernel. @@ -84,8 +84,7 @@ Device Names The following is a list of physical storage devices - supported in FreeBSD, and the device names associated with - them. + supported in &os;, and their associated device names. Physical Disk Naming Conventions @@ -180,21 +179,16 @@ adding - The following section will describe how to add a new + This section describes how to add a new SCSI disk to a machine that currently only - has a single drive. First turn off the computer and install the - drive in the computer following the instructions of the - computer, controller, and drive manufacturer. Due to the wide - variations of procedures to do this, the details are beyond the - scope of this document. - - Login as user root. After you have - installed the drive, inspect - /var/run/dmesg.boot to ensure the new disk - was found. Continuing with our example, the newly added drive - will be da1 and we want to mount it on - /1 (if you are adding an IDE drive, the - device name will be ad1). + has a single drive. First, turn off the computer and install + the drive in the computer following the instructions of the + computer, controller, and drive manufacturers. Reboot + the system and become root. + + Inspect /var/run/dmesg.boot to ensure + the new disk was found. In this example, the newly added SCSI + drive should appear as da1.partitionsslices @@ -202,36 +196,35 @@ fdisk - FreeBSD runs on IBM-PC compatible computers, therefore it - must take into account the PC BIOS partitions. These are + &os; runs on IBM-PC compatible computers, therefore it + must take into account the PC BIOS partitions which are different from the traditional BSD partitions. A PC disk has up to four BIOS partition entries. If the disk is going to be - truly dedicated to FreeBSD, you can use the - dedicated mode. Otherwise, FreeBSD will - have to live within one of the PC BIOS partitions. FreeBSD - calls the PC BIOS partitions slices so as - not to confuse them with traditional BSD partitions. You may - also use slices on a disk that is dedicated to FreeBSD, but used - in a computer that also has another operating system installed. - This is a good way to avoid confusing the - fdisk utility of other, non-FreeBSD operating - systems. + truly dedicated to &os;, use dedicated + mode. Otherwise, &os; will have to live within one of the PC + BIOS partitions. &os; calls the PC BIOS partitions + slices so as not to confuse them with + traditional BSD partitions. Slices may also be used on a disk + that is dedicated to &os;, but used in a computer that also has + another operating system installed. This is a good way to avoid + confusing the fdisk utility of non-&os; + operating systems. - In the slice case the drive will be added as + In the slice case, the drive will be added as /dev/da1s1e. This is read as: SCSI disk, unit number 1 (second SCSI disk), slice 1 (PC BIOS partition 1), and e BSD partition. In the dedicated - case, the drive will be added simply as + case, the drive will be added as /dev/da1e. Due to the use of 32-bit integers to store the number of - sectors, &man.bsdlabel.8; is limited to 2^32-1 sectors per disk + sectors, &man.bsdlabel.8; is limited to 2^32-1 sectors per disk, or 2TB in most cases. The &man.fdisk.8; format allows a starting sector of no more than 2^32-1 and a length of no more - than 2^32-1, limiting partitions to 2TB and disks to 4TB in most - cases. The &man.sunlabel.8; format is limited to 2^32-1 sectors - per partition and 8 partitions for a total of 16TB. For larger - disks, &man.gpart.8; may be used to create + than 2^32-1, limiting partitions to 2TB and disks to 4TB, in + most cases. The &man.sunlabel.8; format is limited to 2^32-1 + sectors per partition and 8 partitions for a total of 16TB. For + larger disks, &man.gpart.8; may be used to create GPT partitions. GPT has the added benefit of not being limited to 4 slices. @@ -249,15 +242,14 @@ Navigating - <application>Sysinstall</application> + sysinstall - You may use sysinstall to partition - and label a new disk using its easy to use menus. Either - login as user root or use the - su command. Run + sysinstall can be used to partition + and label a new disk using its easy-to-use menus. As + root, run sysinstall and enter the Configure menu. Within the - FreeBSD Configuration Menu, scroll down + &os; Configuration Menu, scroll down and select the Fdisk option. @@ -266,14 +258,14 @@ Editor Once inside fdisk, pressing - A will use the entire disk for FreeBSD. - When asked if you want to remain cooperative with + A will use the entire disk for &os;. + When asked whether to remain cooperative with any future possible operating systems, answer YES. Write the changes to the disk - using W. Now exit the FDISK editor by - pressing Q. Next you will be asked about - the Master Boot Record. Since you are - adding a disk to an already running system, choose + using W. Exit the fdisk editor by + pressing Q which will prompt about + the Master Boot Record. Since the disk is + being added to an already running system, choose None. @@ -282,43 +274,43 @@ BSD partitions - Next, you need to exit - sysinstall and start it again. - Follow the directions above, although this time choose the - Label option. This will enter the - Disk Label Editor. This is where you - will create the traditional BSD partitions. A disk can - have up to eight partitions, labeled + Next, exit sysinstall and + start it again. Follow the directions above, except this + time choose the Label option. This + will enter the Disk Label Editor. This + editor is used to create traditional BSD partitions. A + disk can have up to eight partitions, labeled a-h. A few of the partition labels have special uses. The a partition is - used for the root partition (/). - Thus only your system disk (e.g., the disk you boot from) - should have an a partition. The - b partition is used for swap - partitions, and you may have many disks with swap + used for the root partition (/). Only the disk the + system boots from should have an a + partition. The b partition is used for + swap partitions, and there can be many disks with swap partitions. The c partition addresses - the entire disk in dedicated mode, or the entire FreeBSD + the entire disk in dedicated mode, or the entire &os; slice in slice mode. The other partitions are for general use. - sysinstall's Label editor - favors the e partition for non-root, - non-swap partitions. Within the Label editor, create a - single file system by pressing C. When - prompted if this will be a FS (file system) or swap, - choose FS and type in a mount point - (e.g., /mnt). When adding a disk in - post-install mode, sysinstall - will not create entries in /etc/fstab - for you, so the mount point you specify is not - important. - - You are now ready to write the new label to the disk - and create a file system on it. Do this by pressing - W. Ignore any errors from - sysinstall that it could not - mount the new partition. Exit the Label Editor and - sysinstall completely. + The label editor in + sysinstall favors the + e partition for non-root, non-swap + partitions. Within the label editor, create a single file + system by pressing C. When prompted if + this will be a FS (file system) or swap, choose + FS and type in a mount point such as + /mnt). When adding + a disk in post-install mode, + sysinstall will not create + entries in /etc/fstab, so the mount + point you specify is not important. + + Press W to write the new label to the + disk and create a file system on it. Ignore any errors + from sysinstall indicating that + it could not mount the new partition. Exit the label + editor then sysinstall + completely. @@ -337,12 +329,12 @@ Using Slices - This setup will allow your disk to work correctly with - other operating systems that might be installed on your - computer and will not confuse other operating systems' - fdisk utilities. It is recommended - to use this method for new disk installs. Only use - dedicated mode if you have a good reason + The setup in the following example allows the new disk + to work correctly with other operating systems that might be + installed on the computer without confusing other operating + systems' fdisk utilities. This method is + recommended for new disk installs. Only use + dedicated mode if there is a good reason to do so! &prompt.root; dd if=/dev/zero of=/dev/da1 bs=1k count=1 @@ -354,7 +346,7 @@ &prompt.root; mount /dev/da1s1e /1 # Mount the partition(s) &prompt.root; vi /etc/fstab # Add the appropriate entry/entries to your /etc/fstab. - If you have an IDE disk, substitute + For an IDE disk, substitute ad for da. @@ -363,13 +355,11 @@ OS/2 - If you will not be sharing the new drive with another - operating system, you may use the - dedicated mode. Remember this mode can - confuse Microsoft operating systems; however, no damage will - be done by them. IBM's &os2; however, will - appropriate any partition it finds which it - does not understand. + If the new drive will not be shared with another + operating system, dedicated mode can be + used. This mode can confuse Microsoft operating systems; + however, no damage will be done by them. To configure a + disk in dedicated mode: &prompt.root; dd if=/dev/zero of=/dev/da1 bs=1k count=1 &prompt.root; bsdlabel -Bw da1 auto @@ -422,89 +412,78 @@ RAIDsoftware RAIDCCD - When choosing a mass storage solution the most important - factors to consider are speed, reliability, and cost. It is - rare to have all three in balance; normally a fast, reliable - mass storage device is expensive, and to cut back on cost - either speed or reliability must be sacrificed. + When choosing a mass storage solution, the most + important factors to consider are speed, reliability, and + cost. It is rare to have all three in balance. Normally a + fast, reliable mass storage device is expensive, and to cut + back on cost either speed or reliability must be + sacrificed. In designing the system described below, cost was chosen as the most important factor, followed by speed, then reliability. Data transfer speed for this system is - ultimately constrained by the network. And while - reliability is very important, the CCD drive described - below serves online data that is already fully backed up - on CD-R's and can easily be replaced. - - Defining your own requirements is the first step in - choosing a mass storage solution. If your requirements - prefer speed or reliability over cost, your solution will - differ from the system described in this section. + ultimately constrained by the network. While reliability is + very important, the CCD drive described below serves online + data that is already fully backed up and which can easily be + replaced. + + Defining the requirements is the first step in choosing + a mass storage solution. If the requirements prefer speed + or reliability over cost, the solution will differ from the + system described in this section. Installing the Hardware In addition to the IDE system disk, three Western Digital 30GB, 5400 RPM IDE disks form the core of the CCD - disk described below providing approximately 90GB of + disk described below, providing approximately 90GB of online storage. Ideally, each IDE disk would have its own IDE controller and cable, but to minimize cost, additional - IDE controllers were not used. Instead the disks were + IDE controllers were not used. Instead, the disks were configured with jumpers so that each IDE controller has one master, and one slave. Upon reboot, the system BIOS was configured to automatically detect the disks attached. More - importantly, FreeBSD detected them on reboot: + importantly, &os; detected them on reboot:ad0: 19574MB <WDC WD205BA> [39770/16/63] at ata0-master UDMA33 ad1: 29333MB <WDC WD307AA> [59598/16/63] at ata0-slave UDMA33 ad2: 29333MB <WDC WD307AA> [59598/16/63] at ata1-master UDMA33 ad3: 29333MB <WDC WD307AA> [59598/16/63] at ata1-slave UDMA33 - If FreeBSD does not detect all the disks, ensure - that you have jumpered them correctly. Most IDE drives - also have a Cable Select jumper. This is - not the jumper for the master/slave - relationship. Consult the drive documentation for help in - identifying the correct jumper. - - Next, consider how to attach them as part of the file - system. You should research both &man.vinum.4; () and &man.ccd.4;. In this - particular configuration, &man.ccd.4; was chosen. + If &os; does not detect all the disks, consult + the drive documentation for proper setup and verify + that the controller is supported by &os;. Setting Up the CCD - The &man.ccd.4; driver allows you to take several - identical disks and concatenate them into one logical file - system. In order to use &man.ccd.4;, you need a kernel - with &man.ccd.4; support built in. Add this line to your - kernel configuration file, rebuild, and reinstall the - kernel: + The &man.ccd.4; driver takes several identical disks + and concatenates them into one logical file system. In + order to use &man.ccd.4;, its kernel module must be + loaded using &man.ccd.4;. When using a custom kernel, + ensure that this line is compiled in: device ccd - The &man.ccd.4; support can also be loaded as a kernel - loadable module. - - To set up &man.ccd.4;, you must first use - &man.bsdlabel.8; to label the disks: + Before configuring &man.ccd.4;, use &man.bsdlabel.8; + to label the disks: bsdlabel -w ad1 auto bsdlabel -w ad2 auto bsdlabel -w ad3 auto - This creates a bsdlabel for + This example creates a bsdlabel for ad1c, ad2c and ad3c that spans the entire disk. - The next step is to change the disk label type. You - can use &man.bsdlabel.8; to edit the disks: + The next step is to change the disk label type. Use + &man.bsdlabel.8; to edit the disks: bsdlabel -e ad1 bsdlabel -e ad2 @@ -537,46 +516,46 @@ bsdlabel -e ad3 Building the File System - Now that you have all the disks labeled, you must - build the &man.ccd.4;. To do that, use &man.ccdconfig.8;, - with options similar to the following: + Now that all the disks are labeled, build the + &man.ccd.4; using &man.ccdconfig.8;, with options similar + to the following: ccdconfig ccd0 32 0 /dev/ad1e /dev/ad2e /dev/ad3e - The use and meaning of each option is shown + The use and meaning of each option is described below: The first argument is the device to configure, in this case, /dev/ccd0c. The - /dev/ portion is optional. + /dev/ portion is optional. - The interleave for the file system. The - interleave defines the size of a stripe in disk - blocks, each normally 512 bytes. So, an interleave of - 32 would be 16,384 bytes. + The interleave for the file system, which defines + the size of a stripe in disk blocks, each normally 512 + bytes. So, an interleave of 32 would be 16,384 + bytes. - Flags for &man.ccdconfig.8;. If you want to - enable drive mirroring, you can specify a flag here. - This configuration does not provide mirroring for + Flags for &man.ccdconfig.8;. For example, to + enable drive mirroring, specify a flag. This + configuration does not provide mirroring for &man.ccd.4;, so it is set at 0 (zero). The final arguments to &man.ccdconfig.8; are the devices to place into the array. Use the complete - pathname for each device. + path name for each device. After running &man.ccdconfig.8; the &man.ccd.4; is - configured. A file system can be installed. Refer to - &man.newfs.8; for options, or simply run: + configured and a file system can be installed. Refer to + &man.newfs.8; for options, or run: newfs /dev/ccd0c @@ -584,9 +563,9 @@ bsdlabel -e ad3 Making it All Automatic - Generally, you will want to mount the &man.ccd.4; upon - each reboot. To do this, you must configure it first. - Write out your current configuration to + Generally, &man.ccd.4; should be configured to + automount upon each reboot. To do this, write out the + current configuration to /etc/ccd.conf using the following command: @@ -599,9 +578,9 @@ bsdlabel -e ad3 mounted. - If you are booting into single user mode, before you - can &man.mount.8; the &man.ccd.4;, you need to issue the - following command to configure the array: + When booting into single user mode, the following + command must be issued to configure the array before + the &man.ccd.4; can be mounted: ccdconfig -C @@ -634,7 +613,7 @@ bsdlabel -e ad3 storage. &man.vinum.4; implements the RAID-0, RAID-1 and RAID-5 models, both individually and in combination. - See for more + Refer to for more information about &man.vinum.4;. @@ -647,32 +626,31 @@ bsdlabel -e ad3 hardware - FreeBSD also supports a variety of hardware + &os; also supports a variety of hardware RAID controllers. These devices control a - RAID subsystem without the need for FreeBSD + RAID subsystem without the need for &os; specific software to manage the array. Using an on-card BIOS, the card - controls most of the disk operations itself. The following is - a brief setup description using a Promise + controls most of the disk operations. The following is a + brief setup description using a Promise IDE RAID controller. When this card is installed and the system is started up, it displays a prompt requesting information. Follow the - instructions to enter the card's setup screen. From here, you - have the ability to combine all the attached drives. After - doing so, the disk(s) will look like a single drive to - FreeBSD. Other RAID levels can be set up + instructions to enter the card's setup screen and to combine + all the attached drives. After doing so, the disks will + look like a single drive to &os;. Other + RAID levels can be set up accordingly. Rebuilding ATA RAID1 Arrays - FreeBSD allows you to hot-replace a failed disk in an - array. This requires that you catch it before you - reboot. + &os; supports the ability to hot-replace a failed disk in + an array. - You will probably see something like the following in + An error indicating a failed disk will appear in /var/log/messages or in the &man.dmesg.8; output: @@ -684,7 +662,7 @@ ad6: hard error reading fsbn 1116119 of status=59 error=40 ar0: WARNING - mirror lost - Using &man.atacontrol.8;, check for further + Use &man.atacontrol.8; to check for further information: &prompt.root; atacontrol list @@ -709,8 +687,8 @@ ar0: ATA RAID1 subdisks: ad4 ad6 status: - You will first need to detach the ata channel with the - failed disk so you can safely remove it: + First, detach the ata channel with the failed disk + so that it can be safely removed: &prompt.root; atacontrol detach ata3 @@ -779,19 +757,18 @@ ar0: ATA RAID1 subdisks: ad4 ad6 status: disks - A lot of external storage solutions, nowadays, use the - Universal Serial Bus (USB): hard drives, USB thumbdrives, CD-R - burners, etc. &os; provides support for these devices. + Many external storage solutions, such as hard drives, USB + thumbdrives, and CD/DVD burners, use the Universal Serial Bus + (USB). &os; provides support for these devices. Configuration The USB mass storage devices driver, &man.umass.4;, - provides the support for USB storage devices. If you use the - GENERIC kernel, you do not have to change - anything in your configuration. If you use a custom kernel, - be sure that the following lines are present in your kernel - configuration file: + is built into the GENERIC kernel + and provides support for USB storage devices. For a custom + kernel, be sure that the following lines are present in the + kernel configuration file: device scbus device da @@ -802,21 +779,17 @@ device ehci device usb device umass - The &man.umass.4; driver uses the SCSI subsystem to access - to the USB storage devices, your USB device will be seen as a - SCSI device by the system. Depending on the USB chipset on - your motherboard, you only need either device - uhci or device ohci for USB 1.X - support, however having both in the kernel configuration file - is harmless. Support for USB 2.0 controllers is provided by - the &man.ehci.4; driver (the device ehci - line). Do not forget to compile and install the new kernel if - you added any lines. + Since the &man.umass.4; driver uses the SCSI subsystem to + access the USB storage devices, any USB device will be seen as + a SCSI device by the system. Depending on the USB chipset on + the motherboard, device uhci or + device ohci is used to provide USB 1.X + support. Support for USB 2.0 controllers is provided by + device ehci. - If your USB device is a CD-R or DVD burner, the SCSI - CD-ROM driver, &man.cd.4;, must be added to the kernel via - the line: + If the USB device is a CD or DVD burner, &man.cd.4;, + must be added to the kernel via the line: device cd @@ -829,9 +802,9 @@ device umass Testing the Configuration - The configuration is ready to be tested: plug in your USB - device, and in the system message buffer (&man.dmesg.8;), the - drive should appear as something like: + To test the USB configuration, plug in the USB device. In + the system message buffer, &man.dmesg.8;, the drive should + appear as something like: umass0: USB Solid state disk, rev 1.10/1.00, addr 2 GEOM: create disk da0 dp=0xc2d74850 @@ -840,97 +813,91 @@ da0: <Generic Traveling Disk 1.11> da0: 1.000MB/s transfers da0: 126MB (258048 512 byte sectors: 64H 32S/T 126C) - Of course, the brand, the device node - (da0) and other details can differ - according to your configuration. - - Since the USB device is seen as a SCSI one, the - camcontrol command can be used to list the - USB storage devices attached to the system: + The brand, device node (da0), and + other details will differ according to the device. + + Since the USB device is seen as a SCSI one, + camcontrol can be used to list the USB + storage devices attached to the system: &prompt.root; camcontrol devlist <Generic Traveling Disk 1.11> at scbus0 target 0 lun 0 (da0,pass0) - If the drive comes with a file system, you should be able - to mount it. The will help you - to format and create partitions on the USB drive if - needed. + If the drive comes with a file system, it can be mounted. + Refer to for + instructions on how to format and create partitions on the USB + drive. - Allowing untrusted users to mount arbitrary media, - e.g., by enabling vfs.usermount as + Allowing untrusted users to mount arbitrary media, by + enabling vfs.usermount as described below, should not be considered safe from a security point of view. Most file systems in &os; were not built to safeguard against malicious devices. - To make this device mountable as a normal user, certain - steps have to be taken. First, the devices that are created - when a USB storage device is connected need to be accessible - by the user. A solution is to make all users of these devices - a member of the operator group. This - is done with &man.pw.8;. Second, when the devices are - created, the operator group should be - able to read and write them. This is accomplished by adding - these lines to + To make the device mountable as a normal user, one + solution is to make all users of the device a member of the + operator group using &man.pw.8;. + Next, ensure that the operator group is + able to read and write the device by adding these lines to /etc/devfs.rules: [localrules=5] add path 'da*' mode 0660 group operator - If there already are SCSI disks in the system, it must - be done a bit different. E.g., if the system already - contains disks da0 through - da2 attached to the system, change + If SCSI disks are installed in the system, change the second line as follows: add path 'da[3-9]*' mode 0660 group operator - This will exclude the already existing disks from - belonging to the operator - group. + This will exclude the first three SCSI disks + (da0 to + da2)from belonging to the + operator group. - You also have to enable your &man.devfs.rules.5; ruleset - in your /etc/rc.conf file: + Next, enable the &man.devfs.rules.5; ruleset in + /etc/rc.conf: devfs_system_ruleset="localrules" - Next, the kernel has to be configured to allow regular - users to mount file systems. The easiest way is to add the + Next, instruct the running kernel to allow regular users + to mount file systems. The easiest way is to add the following line to /etc/sysctl.conf: vfs.usermount=1 - Note that this only takes effect after the next reboot. - Alternatively, one can also use &man.sysctl.8; to set this - variable. + Since this only takes effect after the next reboot use + &man.sysctl.8; to set this variable now. The final step is to create a directory where the file system is to be mounted. This directory needs to be owned by the user that is to mount the file system. One way to do that is for root to create a subdirectory - owned by that user as - /mnt/username - (replace username by the login name - of the actual user and usergroup by - the user's primary group): + owned by that user as /mnt/username. + In the following example, replace + username with the login name of the + user and usergroup with the user's + primary group: &prompt.root; mkdir /mnt/username &prompt.root; chown username:usergroup /mnt/username Suppose a USB thumbdrive is plugged in, and a device - /dev/da0s1 appears. Since these devices - usually come preformatted with a FAT file system, one can - mount them like this: + /dev/da0s1 appears. If the device is + preformatted with a FAT file system, it can be mounted + using: &prompt.user; mount -t msdosfs -o -m=644,-M=755 /dev/da0s1 /mnt/username - If you unplug the device (the disk must be unmounted - before), you should see, in the system message buffer, - something like the following: + Before the device can be unplugged, it + must be unmounted first. After device + removal, the system message buffer will show messages similar + to the following: umass0: at uhub0 port 1 (addr 2) disconnected (da0:umass-sim0:0:0:0): lost device @@ -964,7 +931,7 @@ umass0: detached - Creating and Using Optical Media (CDs) + Creating and Using CD Media CDROMs @@ -974,18 +941,18 @@ umass0: detached Introduction - CDs have a number of features that differentiate them from - conventional disks. Initially, they were not writable by the - user. They are designed so that they can be read continuously - without delays to move the head between tracks. They are also - much easier to transport between systems than similarly sized - media were at the time. - - CDs do have tracks, but this refers to a section of data - to be read continuously and not a physical property of the - disk. To produce a CD on FreeBSD, you prepare the data files - that are going to make up the tracks on the CD, then write the - tracks to the CD. + CD media provide a number of features that differentiate + them from conventional disks. Initially, they were not + writable by the user. They are designed so that they can be + read continuously without delays to move the head between + tracks. They are also much easier to transport between + systems. + + CD media do have tracks, but this refers to a section of + data to be read continuously and not a physical property of + the disk. For example, to produce a CD on &os;, prepare the + data files that are going to make up the tracks on the CD, + then write the tracks to the CD. ISO 9660 @@ -994,11 +961,10 @@ umass0: detached The ISO 9660 file system was designed to deal with these - differences. It unfortunately codifies file system limits - that were common then. Fortunately, it provides an extension - mechanism that allows properly written CDs to exceed those - limits while still working with systems that do not support - those extensions. + differences. To overcome the original file system limits, it + provides an extension mechanism that allows properly written + CDs to exceed those limits while still working with systems + that do not support those extensions. The sysutils/cdrtools - port includes &man.mkisofs.8;, a program that you can use to - produce a data file containing an ISO 9660 file - system. It has options that support various extensions, and - is described below. + port includes &man.mkisofs.8;, a program that can be used to + produce a data file containing an ISO 9660 file system. It + has options that support various extensions, and is described + below. CD burner ATAPI - Which tool to use to burn the CD depends on whether your + Which tool to use to burn the CD depends on whether the CD burner is ATAPI or something else. ATAPI CD burners use - the burncd - program that is part of the base system. SCSI and USB CD - burners should use - cdrecord - from the sysutils/cdrtools - port. It is also possible to use - cdrecord - and other tools for SCSI drives on ATAPI hardware with the - ATAPI/CAM module. - - If you want CD burning software with a graphical user - interface, you may wish to take a look at either - X-CD-Roast or + burncd + which is part of the base system. SCSI and USB CD burners + should use cdrecord from the + sysutils/cdrtools port. + It is also possible to use cdrecord and other tools + for SCSI drives on ATAPI hardware with the ATAPI/CAM module. + + For CD burning software with a graphical user + interface, consider X-CD-Roast or K3b. These tools are available as packages or from the sysutils/xcdroast and @@ -1044,11 +1009,10 @@ umass0: detached <application>mkisofs</application> - The &man.mkisofs.8; program, which is part of the - sysutils/cdrtools port, - produces an ISO 9660 file system that is an image of a - directory tree in the &unix; file system name space. The - simplest usage is: + The sysutils/cdrtools + port also installs &man.mkisofs.8;, which produces an ISO 9660 + file system that is an image of a directory tree in the &unix; + file system name space. The simplest usage is: &prompt.root; mkisofs -o imagefile.iso /path/to/tree @@ -1057,11 +1021,11 @@ umass0: detached ISO 9660 - This command will create an + This command creates an imagefile.iso containing an ISO 9660 file system that is a copy of the tree at /path/to/tree. In the process, it - will map the file names to names that fit the limitations of + maps the file names to names that fit the limitations of the standard ISO 9660 file system, and will exclude files that have names uncharacteristic of ISO file systems. @@ -1073,19 +1037,19 @@ umass0: detached file systems Joliet - A number of options are available to overcome those + A number of options are available to overcome these restrictions. In particular, enables the Rock Ridge extensions common to &unix; systems, enables Joliet extensions used by Microsoft systems, and can be used to create HFS file systems used by &macos;. - For CDs that are going to be used only on FreeBSD systems, + For CDs that are going to be used only on &os; systems, can be used to disable all filename restrictions. When used with , it produces - a file system image that is identical to the FreeBSD tree you - started from, though it may violate the ISO 9660 standard in a - number of ways. + a file system image that is identical to the specified &os; + tree, though it may violate the ISO 9660 standard in a number + of ways. CDROMs @@ -1096,36 +1060,35 @@ umass0: detached in producing an El Torito bootable CD. This option takes an argument which is the path to a boot image from the top of the tree being written to the CD. By default, - &man.mkisofs.8; creates an ISO image in the so-called - floppy disk emulation mode, and thus expects - the boot image to be exactly 1200, 1440 or 2880 KB in - size. Some boot loaders, like the one used by the FreeBSD - distribution disks, do not use emulation mode; in this case, - the option should be used. So, - if /tmp/myboot holds a bootable FreeBSD - system with the boot image in - /tmp/myboot/boot/cdboot, you could - produce the image of an ISO 9660 file system in - /tmp/bootable.iso like so: + &man.mkisofs.8; creates an ISO image in floppy disk + emulation mode, and thus expects the boot image to + be exactly 1200, 1440 or 2880 KB in size. Some boot + loaders, like the one used by the &os; distribution disks, do + not use emulation mode. In this case, + should be used. So, if + /tmp/myboot holds a + bootable &os; system with the boot image in /tmp/myboot/boot/cdboot, this + command would produce the image of an ISO 9660 file system as + /tmp/bootable.iso: &prompt.root; mkisofs -R -no-emul-boot -b boot/cdboot -o /tmp/bootable.iso /tmp/myboot *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-head@FreeBSD.ORG Thu Feb 7 18:02:01 2013 Return-Path: Delivered-To: svn-doc-head@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 B734D3AF; Thu, 7 Feb 2013 18:02:01 +0000 (UTC) (envelope-from gjb@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 AB4941BB; Thu, 7 Feb 2013 18:02: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 r17I21eg049706; Thu, 7 Feb 2013 18:02:01 GMT (envelope-from gjb@svn.freebsd.org) Received: (from gjb@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r17I21fM049705; Thu, 7 Feb 2013 18:02:01 GMT (envelope-from gjb@svn.freebsd.org) Message-Id: <201302071802.r17I21fM049705@svn.freebsd.org> From: Glen Barber Date: Thu, 7 Feb 2013 18:02:01 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40907 - head/en_US.ISO8859-1/books/handbook/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-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2013 18:02:01 -0000 Author: gjb Date: Thu Feb 7 18:02:01 2013 New Revision: 40907 URL: http://svnweb.freebsd.org/changeset/doc/40907 Log: Fix build. Modified: head/en_US.ISO8859-1/books/handbook/mac/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/mac/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/mac/chapter.xml Thu Feb 7 15:53:27 2013 (r40906) +++ head/en_US.ISO8859-1/books/handbook/mac/chapter.xml Thu Feb 7 18:02:01 2013 (r40907) @@ -405,7 +405,7 @@ returned without error. A common error is Permission denied which usually occurs when the label is being set or modified on an object which is - restricted.Other conditions may produce different + restricted.Other conditions may produce different failures. For instance, the file may not be owned by the user attempting to relabel the object, the object may not exist, or the object may be read only. A mandatory policy @@ -415,7 +415,7 @@ example, a user running at low integrity tries to change the label of a high integrity file. Or perhaps a user running at low integrity tries to change the label of a low - integrity file to a high integrity label. The + integrity file to a high integrity label. The system administrator may use the following commands to overcome this: From owner-svn-doc-head@FreeBSD.ORG Fri Feb 8 00:22:41 2013 Return-Path: Delivered-To: svn-doc-head@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 65D36CEE; Fri, 8 Feb 2013 00:22:41 +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 40185942; Fri, 8 Feb 2013 00:22: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 r180MfYL064911; Fri, 8 Feb 2013 00:22:41 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r180MfNQ064910; Fri, 8 Feb 2013 00:22:41 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201302080022.r180MfNQ064910@svn.freebsd.org> From: Eitan Adler Date: Fri, 8 Feb 2013 00:22:41 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40908 - 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-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 00:22:41 -0000 Author: eadler Date: Fri Feb 8 00:22:40 2013 New Revision: 40908 URL: http://svnweb.freebsd.org/changeset/doc/40908 Log: Remove out of date question Noted by: scottl Approved by: bcr (mentor, implicit) 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 Thu Feb 7 18:02:01 2013 (r40907) +++ head/en_US.ISO8859-1/books/faq/book.xml Fri Feb 8 00:22:40 2013 (r40908) @@ -1421,66 +1421,6 @@ - - Why do I get a panic: can't mount - root error when rebooting the system after - installation? - - - - This error comes from confusion between the boot block's - and the kernel's understanding of the disk devices. The - error usually manifests on two-disk IDE systems, with the - hard disks arranged as the master or single device on - separate IDE controllers, with &os; installed on the - secondary IDE controller. The boot blocks think the system - is installed on ad0 (the second - BIOS disk) while the kernel assigns the first disk on the - secondary controller device, ad2. - After the device probing, the kernel tries to mount what the - boot blocks think is the boot disk, - ad0, while it is really - ad2, and fails. - - To fix the problem, do one of the following: - - - - Reboot the system and hit Enter at - the Booting kernel in 10 seconds; hit [Enter] - to interrupt prompt. This will drop you into - the boot loader. - - Then type - set root_disk_unit="disk_number". - disk_number will be - 0 if &os; is installed on the master - drive on the first IDE controller, 1 - if it is installed on the slave on the first IDE - controller, 2 if it is installed on - the master of the second IDE controller, and - 3 if it is installed on the slave of - the second IDE controller. - - Then type boot, and your - system should boot correctly. - - To make this change permanent (i.e, so you do not - have to do this every time you reboot or turn on your - &os; machine), put the line - root_disk_unit="disk_number" - in /boot/loader.conf.local. - - - - Move the &os; disk onto the primary IDE - controller, so the hard disks are consecutive. - - - - - - What are the limits for memory? From owner-svn-doc-head@FreeBSD.ORG Fri Feb 8 00:22:45 2013 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 59C9ACF1; Fri, 8 Feb 2013 00:22:45 +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 293B6945; Fri, 8 Feb 2013 00:22:45 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r180Mjpk064953; Fri, 8 Feb 2013 00:22:45 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r180Mj3E064952; Fri, 8 Feb 2013 00:22:45 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201302080022.r180Mj3E064952@svn.freebsd.org> From: Eitan Adler Date: Fri, 8 Feb 2013 00:22:44 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40909 - 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-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 00:22:45 -0000 Author: eadler Date: Fri Feb 8 00:22:44 2013 New Revision: 40909 URL: http://svnweb.freebsd.org/changeset/doc/40909 Log: Remove obsolete question Noted by: imp Approved by: bcr (mentor, implicit) 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 Fri Feb 8 00:22:40 2013 (r40908) +++ head/en_US.ISO8859-1/books/faq/book.xml Fri Feb 8 00:22:44 2013 (r40909) @@ -2225,35 +2225,6 @@ bindkey ^[[3~ delete-char # for xterm

- - My system has more than 1 GB of RAM, and I'm - getting panics with kmem_map too small - messages. What is wrong? - - - - Normally, &os; determines a number of kernel parameters, - such as the maximum number of files that can be open - concurrently, from the amount of memory installed in the - system. On systems with one gigabyte of RAM or more, this - auto sizing mechanism may choose values that - are too high: while starting up, the kernel allocates - various tables and other structures that fill up most of the - available kernel memory. Later on, while the system is - running, the kernel has no more space left for dynamic - memory allocations, and panics. - - Compile your own kernel, and add the - to your kernel - configuration file, increasing the maximum size to - 400 MB (). 400 MB appears - to be sufficient for machines with up to 6 GB of - memory. - - - - My system does not have 1 GB of RAM, and &os; still panics with kmem_map too From owner-svn-doc-head@FreeBSD.ORG Fri Feb 8 00:22:47 2013 Return-Path: Delivered-To: svn-doc-head@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 97027D29; Fri, 8 Feb 2013 00:22:47 +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 712F5946; Fri, 8 Feb 2013 00:22: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 r180MlcW064989; Fri, 8 Feb 2013 00:22:47 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r180MlKb064988; Fri, 8 Feb 2013 00:22:47 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201302080022.r180MlKb064988@svn.freebsd.org> From: Eitan Adler Date: Fri, 8 Feb 2013 00:22:47 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40910 - 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-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 00:22:47 -0000 Author: eadler Date: Fri Feb 8 00:22:46 2013 New Revision: 40910 URL: http://svnweb.freebsd.org/changeset/doc/40910 Log: Remove obsolete question Noted by: imp Approved by: bcr (mentor, implicit) 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 Fri Feb 8 00:22:44 2013 (r40909) +++ head/en_US.ISO8859-1/books/faq/book.xml Fri Feb 8 00:22:46 2013 (r40910) @@ -2225,23 +2225,6 @@ bindkey ^[[3~ delete-char # for xterm

- - My system does not have 1 GB of RAM, and &os; still - panics with kmem_map too - small! - - - - The panic indicates that the system ran out of virtual - memory for network buffers (specifically, mbuf clusters). - You can increase the amount of VM available for mbuf - clusters by following the instructions in the Network Limits - section of the Handbook. - - - - Why do I get the error maxproc limit exceeded by uid %i, please see tuning(7) and @@ -2253,9 +2236,8 @@ bindkey ^[[3~ delete-char # for xterm

kern.maxusers &man.sysctl.8; variable. kern.maxusers also affects various other - in-kernel limits, such as network buffers (see this earlier - question). If your machine is heavily loaded, you probably + in-kernel limits, such as network buffers. + If your machine is heavily loaded, you probably want to increase kern.maxusers. This will increase these other system limits in addition to the maximum number of processes. From owner-svn-doc-head@FreeBSD.ORG Fri Feb 8 00:22:50 2013 Return-Path: Delivered-To: svn-doc-head@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 4F78DD49; Fri, 8 Feb 2013 00:22:50 +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 421E3947; Fri, 8 Feb 2013 00:22: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 r180MoLa065031; Fri, 8 Feb 2013 00:22:50 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r180Mog9065030; Fri, 8 Feb 2013 00:22:50 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201302080022.r180Mog9065030@svn.freebsd.org> From: Eitan Adler Date: Fri, 8 Feb 2013 00:22:50 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40911 - 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-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 00:22:50 -0000 Author: eadler Date: Fri Feb 8 00:22:49 2013 New Revision: 40911 URL: http://svnweb.freebsd.org/changeset/doc/40911 Log: This question is unlikely to surprise people anymore. Noted by: alfred Approved by: bcr (mentor, implicit) 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 Fri Feb 8 00:22:46 2013 (r40910) +++ head/en_US.ISO8859-1/books/faq/book.xml Fri Feb 8 00:22:49 2013 (r40911) @@ -8325,27 +8325,6 @@ panic: page fault - - Why has dlsym() stopped working for - ELF executables? - - - - The ELF toolchain does not, by default, make the symbols - defined in an executable visible to the dynamic linker. - Consequently dlsym() searches on - handles obtained from calls to dlopen(NULL, - flags) will fail to find such symbols. - - If you want to search, using - dlsym(), for symbols present in the - main executable of a process, you need to link the - executable using the - option to the ELF linker (&man.ld.1;). - - - - How can I increase or reduce the kernel address space on i386? From owner-svn-doc-head@FreeBSD.ORG Fri Feb 8 01:17:03 2013 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id CDAACD11; Fri, 8 Feb 2013 01:17:03 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id 318C2C1D; Fri, 8 Feb 2013 01:17:03 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.6/8.14.6) with ESMTP id r181Gwmn070397; Fri, 8 Feb 2013 03:16:58 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.7.4 kib.kiev.ua r181Gwmn070397 Received: (from kostik@localhost) by tom.home (8.14.6/8.14.6/Submit) id r181Gws3070396; Fri, 8 Feb 2013 03:16:58 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 8 Feb 2013 03:16:58 +0200 From: Konstantin Belousov To: Eitan Adler Subject: Re: svn commit: r40911 - head/en_US.ISO8859-1/books/faq Message-ID: <20130208011658.GP2522@kib.kiev.ua> References: <201302080022.r180Mog9065030@svn.freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="o2FFsPZloSkl7LfN" Content-Disposition: inline In-Reply-To: <201302080022.r180Mog9065030@svn.freebsd.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home Cc: svn-doc-head@freebsd.org, svn-doc-all@freebsd.org, doc-committers@freebsd.org X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 01:17:03 -0000 --o2FFsPZloSkl7LfN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 08, 2013 at 12:22:50AM +0000, Eitan Adler wrote: > Author: eadler > Date: Fri Feb 8 00:22:49 2013 > New Revision: 40911 > URL: http://svnweb.freebsd.org/changeset/doc/40911 >=20 > Log: > This question is unlikely to surprise people anymore. This is often asked, and explanation is correct and well done. Why did you removed it ? > =20 > Noted by: alfred > Approved by: bcr (mentor, implicit) >=20 > Modified: > head/en_US.ISO8859-1/books/faq/book.xml >=20 > Modified: head/en_US.ISO8859-1/books/faq/book.xml > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D > --- head/en_US.ISO8859-1/books/faq/book.xml Fri Feb 8 00:22:46 2013 (r40= 910) > +++ head/en_US.ISO8859-1/books/faq/book.xml Fri Feb 8 00:22:49 2013 (r40= 911) > @@ -8325,27 +8325,6 @@ panic: page fault > > =20 > > - > - Why has dlsym() stopped working for > - ELF executables? > - > - > - > - The ELF toolchain does not, by default, make the symbols > - defined in an executable visible to the dynamic linker. > - Consequently dlsym() searches on > - handles obtained from calls to dlopen(NULL, > - flags) will fail to find such symbols. > - > - If you want to search, using > - dlsym(), for symbols present in the > - main executable of a process, you need to link the > - executable using the > - option to the ELF linker (&man.ld.1;). > - > - > - > - > > How can I increase or reduce the kernel address space on > i386? > _______________________________________________ > svn-doc-all@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/svn-doc-all > To unsubscribe, send any mail to "svn-doc-all-unsubscribe@freebsd.org" --o2FFsPZloSkl7LfN Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQIcBAEBAgAGBQJRFFIKAAoJEJDCuSvBvK1B8GEP/j5tEVm80fgenbn5rMWnMV15 zE0T+Olc8CSv7Y2Obj1GFycgJCUO20mpl77RCLPR+DOsyIxnUQ/Jb5AAgDBsL2Rr WSXTfxWcgjC196QFzrbBctDPyNrhJ6sGZjP/uqdSCSwlDAYMdvRyfkzevsmw2cmG zK/9ljL7irfoU6Y13Rf4RY7mDjEY2XWvjKSwse80opE1kzMvaxSb7NKLLkrEhrwH cNn4J7AgKkbk7c+lnKKj/GVvGFKklvFXUBzAeuT6eydiTt1+s+dkkDWq/S/ESpCD hV9XSxIff/34/0HLOd+Z2SBahBHfXW9oR9TWMuEwdyk09X4/oI7O/Lulrc9TuRvH cLCBI8jK5WQEG7sNHDcAIyJY8Egw68U8qxgn9LOIcMX4ZJuxTViR+uSerXeAsqeF CQZwS9Vcg1Q4Qt27d6gYVwgM+LaAKeFztF9Mq9mXTNQX379wsy+vBlCXT9JOyxJE 9Z+il6ewDEwmb15SaX4Esb7xwKVG5qcBSZWmHUDkrM7vUpi50Xte6GGJj/3RrrB1 mWww6kpxA8S2kR9ujjhdRf+0+Bv5vQ25+EfmtXvtv4E2fZ8g85Sl50Kyw7BNpl3H 4dk9niDXSopQFYj0nvPLWJ57a4IaVM9VSHsWK3+iLQK0oh5R+C1HNwCgPdJJkuV+ YyuxCe+Q/BJWESYnA/k9 =giWo -----END PGP SIGNATURE----- --o2FFsPZloSkl7LfN-- From owner-svn-doc-head@FreeBSD.ORG Fri Feb 8 02:20:20 2013 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A9925E73 for ; Fri, 8 Feb 2013 02:20:20 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-da0-f42.google.com (mail-da0-f42.google.com [209.85.210.42]) by mx1.freebsd.org (Postfix) with ESMTP id 77D96E46 for ; Fri, 8 Feb 2013 02:20:20 +0000 (UTC) Received: by mail-da0-f42.google.com with SMTP id z17so1540448dal.1 for ; Thu, 07 Feb 2013 18:20:14 -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=Khq40i1dg4VNFbldjkYiwVjLuXmj1ozKVLddQ9qvWrI=; b=s8REiXrZ6YOgzpZ8el/x9z4eYx+1Qx2ExoNvJ8I5r3idHyUqPYXeIxY2FmWPek+vVx JvGxGEG6+VAx/TKjzCMt/5YHkPOI9Nsf/sbpqDdeu4N3NWhzveNOqh3TnhFD7HCkXDZR Rgh1mbsXENqcfYW5+XSsWGUToJPjqi0P6Xdkk= 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=Khq40i1dg4VNFbldjkYiwVjLuXmj1ozKVLddQ9qvWrI=; b=j8Ajq6gqSvP7L05mc9FgNqoa0YuwSOpO7UXB+fRb3XuNoe5GPOVN8GYGRA8IqiDZgO PseMUoa6aD8xo3qBaSVA/n0Z9IZNCV7IUZpzWDsQqAuvvrRXU5Oj2p5EWUMuyO96YWOC N0Qi3iYpg+JRNcEWWHKQZ9j4JOPGBsxX5l0jwcCMEA2lKG2PHsnOfS5WaniNoOSZ0Eq8 Gc3+5rKtSW5hQMmJdTC/gzN40cCHLeG3rIh35qDrcf789zjnTNprVpE4TqLMH1E8uNzb 3z8EK/PfrkdBjOAbcDpf89sKqKyHcwbKZiM5blLBHbtJCoAknAdqtK3aiY1B66IhqOxL V61A== X-Received: by 10.66.76.42 with SMTP id h10mr11928599paw.59.1360290014074; Thu, 07 Feb 2013 18:20:14 -0800 (PST) MIME-Version: 1.0 Sender: lists@eitanadler.com Received: by 10.66.148.10 with HTTP; Thu, 7 Feb 2013 18:19:43 -0800 (PST) In-Reply-To: <20130208011658.GP2522@kib.kiev.ua> References: <201302080022.r180Mog9065030@svn.freebsd.org> <20130208011658.GP2522@kib.kiev.ua> From: Eitan Adler Date: Thu, 7 Feb 2013 21:19:43 -0500 X-Google-Sender-Auth: wvmQgFXs011-VBJRPA78KJNWyFo Message-ID: Subject: Re: svn commit: r40911 - head/en_US.ISO8859-1/books/faq To: Konstantin Belousov Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQlDqPs8UQsSR1HzD+z7Jr5C7AQFRpwBxnc882L2vFsXVO7yh4lVjYMD4KpEqseQdy8ml1Z8 Cc: svn-doc-head@freebsd.org, svn-doc-all@freebsd.org, doc-committers@freebsd.org X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 02:20:20 -0000 On 7 February 2013 20:16, Konstantin Belousov wrote: > On Fri, Feb 08, 2013 at 12:22:50AM +0000, Eitan Adler wrote: >> Author: eadler >> Date: Fri Feb 8 00:22:49 2013 >> New Revision: 40911 >> URL: http://svnweb.freebsd.org/changeset/doc/40911 >> >> Log: >> This question is unlikely to surprise people anymore. > This is often asked, and explanation is correct and well done. I was unaware of this. > Why did you removed it ? alfred@ told me that "This question is unlikely to surprise people anymore." I intentionally keep my question-removal commits small and per-question in order that they be easily revertible. Shall I do so for this one? -- Eitan Adler Source, Ports, Doc committer Bugmeister, Ports Security teams From owner-svn-doc-head@FreeBSD.ORG Fri Feb 8 05:46:50 2013 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 484A9BBE; Fri, 8 Feb 2013 05:46:50 +0000 (UTC) (envelope-from jgh@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 224DE6AE; Fri, 8 Feb 2013 05:46: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 r185ko1l062442; Fri, 8 Feb 2013 05:46:50 GMT (envelope-from jgh@svn.freebsd.org) Received: (from jgh@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r185knKv062441; Fri, 8 Feb 2013 05:46:50 GMT (envelope-from jgh@svn.freebsd.org) Message-Id: <201302080546.r185knKv062441@svn.freebsd.org> From: Jason Helfman Date: Fri, 8 Feb 2013 05:46:49 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40912 - head/en_US.ISO8859-1/articles/contributors X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 05:46:50 -0000 Author: jgh (ports committer) Date: Fri Feb 8 05:46:49 2013 New Revision: 40912 URL: http://svnweb.freebsd.org/changeset/doc/40912 Log: - add cyclaero@gmail.com for sysutils/clone PR: 175945 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 Fri Feb 8 00:22:49 2013 (r40911) +++ head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Fri Feb 8 05:46:49 2013 (r40912) @@ -8797,6 +8797,11 @@ + Dr. Rolf Jansen + cyclaero@gmail.com + + + Roman Neuhauser neuhauser@chello.cz From owner-svn-doc-head@FreeBSD.ORG Fri Feb 8 09:46:03 2013 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C28BB5A0; Fri, 8 Feb 2013 09:46:03 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id 0CCB6899; Fri, 8 Feb 2013 09:46:02 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.6/8.14.6) with ESMTP id r189jw0m026922; Fri, 8 Feb 2013 11:45:58 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.7.4 kib.kiev.ua r189jw0m026922 Received: (from kostik@localhost) by tom.home (8.14.6/8.14.6/Submit) id r189jw54026921; Fri, 8 Feb 2013 11:45:58 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 8 Feb 2013 11:45:58 +0200 From: Konstantin Belousov To: Eitan Adler Subject: Re: svn commit: r40911 - head/en_US.ISO8859-1/books/faq Message-ID: <20130208094558.GQ2522@kib.kiev.ua> References: <201302080022.r180Mog9065030@svn.freebsd.org> <20130208011658.GP2522@kib.kiev.ua> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vw/GEePxV8pVp8Qw" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home Cc: svn-doc-head@freebsd.org, svn-doc-all@freebsd.org, doc-committers@freebsd.org X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 09:46:03 -0000 --vw/GEePxV8pVp8Qw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 07, 2013 at 09:19:43PM -0500, Eitan Adler wrote: > On 7 February 2013 20:16, Konstantin Belousov wrote: > > On Fri, Feb 08, 2013 at 12:22:50AM +0000, Eitan Adler wrote: > >> Author: eadler > >> Date: Fri Feb 8 00:22:49 2013 > >> New Revision: 40911 > >> URL: http://svnweb.freebsd.org/changeset/doc/40911 > >> > >> Log: > >> This question is unlikely to surprise people anymore. > > This is often asked, and explanation is correct and well done. >=20 > I was unaware of this. >=20 > > Why did you removed it ? >=20 > alfred@ told me that "This question is unlikely to surprise people anymor= e." >=20 > I intentionally keep my question-removal commits small and > per-question in order that they be easily revertible. Shall I do so > for this one? I recommend to revert this removal. Despite even mentioned in notes section of the dlopen(3), this appears regularly on several lists. --vw/GEePxV8pVp8Qw Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQIcBAEBAgAGBQJRFMlVAAoJEJDCuSvBvK1BkPoP/jNQTiRGaeCngFldruilOHo3 jXenAHy/5h0vbiN2EIsgDg2Wzu2muv7zEMIbpcUWJBQPHZAmzfzAI4FZY60+uUg1 e1NIE59/D7jcFtBhSxTSy+6af4vQCWyCI9y/W2nxTeT6h6yHXKzkBlyNMP0h2fDX N37SeU5yGlfy+VUOhlZhkEQ4v5AzWRc6tD6t4nmNs72wUnoEo89bcluBFTjq47Qg 3lJMDiUZ+ULyKp/d4eIOnGSeRJ/Fsl7fnOWK0rMWkGDmS4C//uI56K2gGimsw7Ut VNJAeWdngnLc65XPHqGG2bx4KQqDI0OUSGovBDlszVztefdMgPw5PjQZ/nrNqyhI Vp5PLI7oEfJ7oNXT/a4HQcTnKrfY1sVCO6qhmUIIN+z1uLoOb/ISlU9FgAaynFsJ r3KZhNKGlb7j6R+QNcUW3+xeyPtL+P1eTH7pPl63pacIuwFRcVf8N/m6KnOqPsbs zid7K3HcUkT1X0ultbuEEFugsKkZEQOhOLSk2yyH0jbKX4rjo0zAHwe29K/KyQUe xeQoQ2AOIea5/XYe6xv0eNUlnqSXaHWq8XeHA9maqUD9wbcas1hBrARnnHSEQNmQ +/Qx1sw/INyIBWB2i+2Tru0/Yxd0UlXsoL2RECad23UOIcpzg+0ODzUW8i00lDng jJZhaFKqYsGxBDmaWbjY =Y3/d -----END PGP SIGNATURE----- --vw/GEePxV8pVp8Qw-- From owner-svn-doc-head@FreeBSD.ORG Fri Feb 8 10:23:04 2013 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9535411D; Fri, 8 Feb 2013 10:23:04 +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 7E19AA0A; Fri, 8 Feb 2013 10:23:04 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r18AN462049815; Fri, 8 Feb 2013 10:23:04 GMT (envelope-from ryusuke@svn.freebsd.org) Received: (from ryusuke@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r18AN4Lm049814; Fri, 8 Feb 2013 10:23:04 GMT (envelope-from ryusuke@svn.freebsd.org) Message-Id: <201302081023.r18AN4Lm049814@svn.freebsd.org> From: Ryusuke SUZUKI Date: Fri, 8 Feb 2013 10:23:04 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40913 - head/ja_JP.eucJP/share/xml X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 10:23:04 -0000 Author: ryusuke Date: Fri Feb 8 10:23:03 2013 New Revision: 40913 URL: http://svnweb.freebsd.org/changeset/doc/40913 Log: - Merge the following from the English version: r40721 -> r40903 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 Fri Feb 8 05:46:49 2013 (r40912) +++ head/ja_JP.eucJP/share/xml/news.xml Fri Feb 8 10:23:03 2013 (r40913) @@ -20,7 +20,7 @@ the contents of will be preferred over <p>. $FreeBSD$ - Original revision: r40721 + Original revision: r40903 --> <news> <cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS"> @@ -34,6 +34,14 @@ <name>1</name> <day> + <name>23</name> + <event> + <p>¿·¥³¥ß¥Ã¥¿½¢Ç¤: + <a href="mailto:achim@FreeBSD.org">Achim Leubner</a> (src)</p> + </event> + </day> + + <day> <name>22</name> <event> <p>¿·¥³¥ß¥Ã¥¿½¢Ç¤: From owner-svn-doc-head@FreeBSD.ORG Fri Feb 8 13:20:52 2013 Return-Path: <owner-svn-doc-head@FreeBSD.ORG> Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 20AD76B5; Fri, 8 Feb 2013 13:20:52 +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 1355062E; Fri, 8 Feb 2013 13:20: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 r18DKpbt004007; Fri, 8 Feb 2013 13:20:51 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r18DKpnW004006; Fri, 8 Feb 2013 13:20:51 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201302081320.r18DKpnW004006@svn.freebsd.org> From: Eitan Adler <eadler@FreeBSD.org> Date: Fri, 8 Feb 2013 13:20:51 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40914 - 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-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head <svn-doc-head.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-head>, <mailto:svn-doc-head-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-head> List-Post: <mailto:svn-doc-head@freebsd.org> List-Help: <mailto:svn-doc-head-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-head>, <mailto:svn-doc-head-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 08 Feb 2013 13:20:52 -0000 Author: eadler Date: Fri Feb 8 13:20:51 2013 New Revision: 40914 URL: http://svnweb.freebsd.org/changeset/doc/40914 Log: Restore dlsym-failure as this question appears to still be an FAQ. Requested by: kib Approved by: bcr (mentor, implicit) 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 Fri Feb 8 10:23:03 2013 (r40913) +++ head/en_US.ISO8859-1/books/faq/book.xml Fri Feb 8 13:20:51 2013 (r40914) @@ -8325,6 +8325,27 @@ panic: page fault</programlisting> </qandaentry> <qandaentry> + <question id="dlsym-failure"> + <para>Why has <function>dlsym()</function> stopped working for + ELF executables?</para> + </question> + + <answer> + <para>The ELF toolchain does not, by default, make the symbols + defined in an executable visible to the dynamic linker. + Consequently <function>dlsym()</function> searches on + handles obtained from calls to <function>dlopen(NULL, + flags)</function> will fail to find such symbols.</para> + + <para>If you want to search, using + <function>dlsym()</function>, for symbols present in the + main executable of a process, you need to link the + executable using the <option>--export-dynamic</option> + option to the ELF linker (&man.ld.1;).</para> + </answer> + </qandaentry> + + <qandaentry> <question id="change-kernel-address-space"> <para>How can I increase or reduce the kernel address space on i386?</para> From owner-svn-doc-head@FreeBSD.ORG Fri Feb 8 19:08:35 2013 Return-Path: <owner-svn-doc-head@FreeBSD.ORG> Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 33528F91; Fri, 8 Feb 2013 19:08: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 2552B997; Fri, 8 Feb 2013 19:08: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 r18J8YQ9006586; Fri, 8 Feb 2013 19:08:34 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r18J8YtM006584; Fri, 8 Feb 2013 19:08:34 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201302081908.r18J8YtM006584@svn.freebsd.org> From: Eitan Adler <eadler@FreeBSD.org> Date: Fri, 8 Feb 2013 19:08:34 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40915 - 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-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head <svn-doc-head.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-head>, <mailto:svn-doc-head-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-head> List-Post: <mailto:svn-doc-head@freebsd.org> List-Help: <mailto:svn-doc-head-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-head>, <mailto:svn-doc-head-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 08 Feb 2013 19:08:35 -0000 Author: eadler Date: Fri Feb 8 19:08:34 2013 New Revision: 40915 URL: http://svnweb.freebsd.org/changeset/doc/40915 Log: Eliminate the last use of 'basically' in the FAQ. Note that this question needs a rewrite, but the goal of this commit is to make igor less noisy (with -y) until that happens. 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 Fri Feb 8 13:20:51 2013 (r40914) +++ head/en_US.ISO8859-1/books/faq/book.xml Fri Feb 8 19:08:34 2013 (r40915) @@ -6014,7 +6014,7 @@ Key F15 A A Menu Wo <listitem> <para>A process which is placed inside a simulation of the - machine. This is more hard-core. Basically it means + machine. It means that someone who is able to break into the process may believe that he can break into the wider machine but is, in fact, only breaking into a simulation of that machine From owner-svn-doc-head@FreeBSD.ORG Fri Feb 8 19:08:37 2013 Return-Path: <owner-svn-doc-head@FreeBSD.ORG> Delivered-To: svn-doc-head@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 37F62F92; Fri, 8 Feb 2013 19:08:37 +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 11A20998; Fri, 8 Feb 2013 19:08: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 r18J8alB006623; Fri, 8 Feb 2013 19:08:36 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r18J8aHm006622; Fri, 8 Feb 2013 19:08:36 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201302081908.r18J8aHm006622@svn.freebsd.org> From: Eitan Adler <eadler@FreeBSD.org> Date: Fri, 8 Feb 2013 19:08:36 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40916 - 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-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head <svn-doc-head.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-head>, <mailto:svn-doc-head-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-head> List-Post: <mailto:svn-doc-head@freebsd.org> List-Help: <mailto:svn-doc-head-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-head>, <mailto:svn-doc-head-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 08 Feb 2013 19:08:37 -0000 Author: eadler Date: Fri Feb 8 19:08:36 2013 New Revision: 40916 URL: http://svnweb.freebsd.org/changeset/doc/40916 Log: Fix a few style errors reported by igor. igor -RabfswcnotS book.xml now reports no problems. This is primarily a whitespace and gramma change but translators may want to double check. 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 Fri Feb 8 19:08:34 2013 (r40915) +++ head/en_US.ISO8859-1/books/faq/book.xml Fri Feb 8 19:08:36 2013 (r40916) @@ -3117,7 +3117,7 @@ kern.sched.name: ULE</screen> this.</para> <para>Alternatively, partition and label the new disk with either - &man.sade.8; or &man.gpart.8;. If the disks are MBR-formatted, + &man.sade.8; or &man.gpart.8;. If the disks are MBR-formatted, you can also install booteasy on both disks with &man.boot0cfg.8;, so that you can dual boot to the old or new system after the copying is done.</para> @@ -4401,9 +4401,9 @@ options SYSVMSG # enable for required to boot from a &os; installation disk, choose the <guimenuitem>Live CD</guimenuitem> or <guimenuitem>Shell</guimenuitem> at the beginning of the install - process and issue the commands mentioned above. You will need to + process and issue the commands mentioned above. You will need to mount the specific partition in this case and then chroot to it, - i.e. replace <command>mount -urw /</command> by + i.e., replace <command>mount -urw /</command> by <command>mount /dev/ada0p1 /mnt; chroot /mnt</command> for a system on <replaceable>ada0p1</replaceable>.</para> </note> @@ -6022,7 +6022,7 @@ Key F15 A A Menu Wo <para>The most common way to accomplish this is to build a simulated environment in a subdirectory and then run the - processes in that directory chroot'd (i.e., <filename + processes in that directory chrooted (i.e., <filename class="directory">/</filename> for that process is this directory, not the real <filename class="directory">/</filename> of the system).</para> From owner-svn-doc-head@FreeBSD.ORG Sat Feb 9 16:21:02 2013 Return-Path: <owner-svn-doc-head@FreeBSD.ORG> Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7C0D1B89; Sat, 9 Feb 2013 16:21:02 +0000 (UTC) (envelope-from jkois@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 6E59E16E; Sat, 9 Feb 2013 16:21: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 r19GL04Z090495; Sat, 9 Feb 2013 16:21:00 GMT (envelope-from jkois@svn.freebsd.org) Received: (from jkois@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r19GL0aj090494; Sat, 9 Feb 2013 16:21:00 GMT (envelope-from jkois@svn.freebsd.org) Message-Id: <201302091621.r19GL0aj090494@svn.freebsd.org> From: Johann Kois <jkois@FreeBSD.org> Date: Sat, 9 Feb 2013 16:21:00 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40917 - head/de_DE.ISO8859-1/share/xml X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head <svn-doc-head.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-head>, <mailto:svn-doc-head-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-head> List-Post: <mailto:svn-doc-head@freebsd.org> List-Help: <mailto:svn-doc-head-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-head>, <mailto:svn-doc-head-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 09 Feb 2013 16:21:02 -0000 Author: jkois Date: Sat Feb 9 16:21:00 2013 New Revision: 40917 URL: http://svnweb.freebsd.org/changeset/doc/40917 Log: r40659 -> r40903 MFde: Resync the project news. Obtained from: The FreeBSD German Documentation Project Modified: head/de_DE.ISO8859-1/share/xml/news.xml Modified: head/de_DE.ISO8859-1/share/xml/news.xml ============================================================================== --- head/de_DE.ISO8859-1/share/xml/news.xml Fri Feb 8 19:08:36 2013 (r40916) +++ head/de_DE.ISO8859-1/share/xml/news.xml Sat Feb 9 16:21:00 2013 (r40917) @@ -4,7 +4,7 @@ <!-- $FreeBSD$ $FreeBSDde$ - basiert auf: r40659 + basiert auf: r40903 --> <!-- Simple schema for FreeBSD Project news. @@ -42,12 +42,30 @@ <name>1</name> <day> - <name>16</name> + <name>23</name> <event> - <p>Neuer Committer: <a + <p>Neuer Committer: <a + href="mailto:achim@FreeBSD.org">Achim Leubner</a> (src)</p> + </event> + </day> + + <day> + <name>22</name> + + <event> + <p>Neuer Committer: <a + href="mailto:dru@FreeBSD.org">Dru Lavigne</a> (doc)</p> + </event> + </day> + + <day> + <name>16</name> + + <event> + <p>Neuer Committer: <a href="mailto:carl@FreeBSD.org">Carl Delsey</a> (src)</p> - </event> + </event> </day> <day> @@ -127,6 +145,15 @@ href="http://freebsdfoundation.blogspot.com/2013/01/faces-of-freebsd-thomas-abthorpe.html">hier.</a></p> </event> </day> + + <day> + <name>7</name> + + <event> + <p>Neuer Committer: <a + href="mailto:ian@FreeBSD.org">Ian Lepore</a> (src)</p> + </event> + </day> </month> </year> @@ -160,6 +187,15 @@ </day> <day> + <name>24</name> + + <event> + <p>Neuer Committer: <a + href="mailto:koobs@FreeBSD.org">Kubilay Kocak</a> (ports)</p> + </event> + </day> + + <day> <name>20</name> <event> From owner-svn-doc-head@FreeBSD.ORG Sat Feb 9 16:46:45 2013 Return-Path: <owner-svn-doc-head@FreeBSD.ORG> Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7C6BD194; Sat, 9 Feb 2013 16:46:45 +0000 (UTC) (envelope-from jkois@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 6EDF4226; Sat, 9 Feb 2013 16:46:45 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r19GkjmJ097087; Sat, 9 Feb 2013 16:46:45 GMT (envelope-from jkois@svn.freebsd.org) Received: (from jkois@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r19Gki6A097083; Sat, 9 Feb 2013 16:46:44 GMT (envelope-from jkois@svn.freebsd.org) Message-Id: <201302091646.r19Gki6A097083@svn.freebsd.org> From: Johann Kois <jkois@FreeBSD.org> Date: Sat, 9 Feb 2013 16:46:44 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40918 - head/de_DE.ISO8859-1/share/xml X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head <svn-doc-head.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-head>, <mailto:svn-doc-head-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-head> List-Post: <mailto:svn-doc-head@freebsd.org> List-Help: <mailto:svn-doc-head-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-head>, <mailto:svn-doc-head-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 09 Feb 2013 16:46:45 -0000 Author: jkois Date: Sat Feb 9 16:46:44 2013 New Revision: 40918 URL: http://svnweb.freebsd.org/changeset/doc/40918 Log: r40251 -> r40864 Resync the german version of this document. Obtained from: The FreeBSD German Documentation Project Modified: head/de_DE.ISO8859-1/share/xml/press.xml Modified: head/de_DE.ISO8859-1/share/xml/press.xml ============================================================================== --- head/de_DE.ISO8859-1/share/xml/press.xml Sat Feb 9 16:21:00 2013 (r40917) +++ head/de_DE.ISO8859-1/share/xml/press.xml Sat Feb 9 16:46:44 2013 (r40918) @@ -7,7 +7,7 @@ "freefall:/c/www/bsddoc/press/". $FreeBSD$ $FreeBSDde$ - basiert auf: r40251 + basiert auf: r40864 --> <press> @@ -16,6 +16,26 @@ </cvs:keyword> <year> + <name>2013</name> + + <month> + <name>1</name> + + <story> + <name>A Decade of OS Access-control Extensibility</name> + <url>https://queue.acm.org/detail.cfm?id=2430732</url> + <site-name>ACM Queue</site-name> + <site-url>https://queue.acm.org/</site-url> + <date>18. Januar 2013</date> + <author>Robert N. M. Watson</author> + <p>Wer sich näher mit der Absicherung von Betriebssystemen + beschäftigt, ist erstaunt über die zahlreichen in der + Praxis eingesetzten Modelle zur Zugangskontrolle.</p> + </story> + </month> + </year> + + <year> <name>2012</name> <month> From owner-svn-doc-head@FreeBSD.ORG Sat Feb 9 17:06:24 2013 Return-Path: <owner-svn-doc-head@FreeBSD.ORG> Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B1BCA71E; Sat, 9 Feb 2013 17:06:24 +0000 (UTC) (envelope-from jkois@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 A45772CB; Sat, 9 Feb 2013 17:06: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 r19H6OE9003358; Sat, 9 Feb 2013 17:06:24 GMT (envelope-from jkois@svn.freebsd.org) Received: (from jkois@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r19H6Od8003357; Sat, 9 Feb 2013 17:06:24 GMT (envelope-from jkois@svn.freebsd.org) Message-Id: <201302091706.r19H6Od8003357@svn.freebsd.org> From: Johann Kois <jkois@FreeBSD.org> Date: Sat, 9 Feb 2013 17:06:24 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40919 - head/de_DE.ISO8859-1/htdocs X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head <svn-doc-head.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-head>, <mailto:svn-doc-head-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-head> List-Post: <mailto:svn-doc-head@freebsd.org> List-Help: <mailto:svn-doc-head-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-head>, <mailto:svn-doc-head-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 09 Feb 2013 17:06:24 -0000 Author: jkois Date: Sat Feb 9 17:06:24 2013 New Revision: 40919 URL: http://svnweb.freebsd.org/changeset/doc/40919 Log: r31588 -> r40760 Resnc. Obtained from: The FreeBSD German Documentation Project Modified: head/de_DE.ISO8859-1/htdocs/about.xml Modified: head/de_DE.ISO8859-1/htdocs/about.xml ============================================================================== --- head/de_DE.ISO8859-1/htdocs/about.xml Sat Feb 9 16:46:44 2013 (r40918) +++ head/de_DE.ISO8859-1/htdocs/about.xml Sat Feb 9 17:06:24 2013 (r40919) @@ -1,8 +1,8 @@ <?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//FreeBSD//DTD XHTML 1.0 Transitional-Based Extension//EN" "http://www.FreeBSD.org/XML/doc/share/xml/xhtml10-freebsd.dtd" [ -<!ENTITY dedate "$FreeBSDde: de-www/about.xml,v 1.13 2008/03/24 15:33:41 jkois Exp $"> -<!ENTITY reference "basiert auf: 1.13"> +<!ENTITY dedate "$FreeBSDde$"> +<!ENTITY reference "basiert auf: r40760"> <!ENTITY title "Über FreeBSD"> ]> @@ -64,7 +64,7 @@ <h2>Viele Anwendungen</h2> - <p>Mit über 17.000 portierten Bibliotheken und <a + <p>Mit über 24.000 portierten Bibliotheken und <a href="&base;/applications.html">Anwendungen</a> eignet sich FreeBSD hervorragend als Betriebssystem für Desktop- und Serversysteme sowie eingebettete Systeme.</p>