From owner-svn-doc-all@FreeBSD.ORG Sat May 24 15:24:59 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0C58D450; Sat, 24 May 2014 15:24:59 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EDE83243C; Sat, 24 May 2014 15:24:58 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s4OFOw2C051568; Sat, 24 May 2014 15:24:58 GMT (envelope-from bcr@svn.freebsd.org) Received: (from bcr@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s4OFOwHZ051567; Sat, 24 May 2014 15:24:58 GMT (envelope-from bcr@svn.freebsd.org) Message-Id: <201405241524.s4OFOwHZ051567@svn.freebsd.org> From: Benedict Reuschling Date: Sat, 24 May 2014 15:24:58 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44935 - head/en_US.ISO8859-1/articles/nanobsd X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 May 2014 15:24:59 -0000 Author: bcr Date: Sat May 24 15:24:58 2014 New Revision: 44935 URL: http://svnweb.freebsd.org/changeset/doc/44935 Log: Remove redundant markup and words around filename tags. Sprinkle capitalizations over title tags to make igor happy. Whitespace fixes will follow next. Modified: head/en_US.ISO8859-1/articles/nanobsd/article.xml Modified: head/en_US.ISO8859-1/articles/nanobsd/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/nanobsd/article.xml Sat May 24 15:13:09 2014 (r44934) +++ head/en_US.ISO8859-1/articles/nanobsd/article.xml Sat May 24 15:24:58 2014 (r44935) @@ -86,7 +86,7 @@ NanoBSD Howto - The design of NanoBSD + The Design of NanoBSD Once the image is present on the medium, it is possible to boot NanoBSD. The mass storage @@ -121,7 +121,7 @@ are expected to persist after the system restarts. - Making persistent changes to <filename>/etc/resolv.conf</filename> + Making Persistent Changes to <filename>/etc/resolv.conf</filename> &prompt.root; vi /etc/resolv.conf [...] @@ -140,13 +140,13 @@ all times is not a good idea, especially if the NanoBSD system runs off a mass storage medium that may be adversely affected by a large number - of writes to the partition (i.e. when the filesystem syncer + of writes to the partition (like when the filesystem syncer flushes data to the system disks). - Building a NanoBSD image + Building a NanoBSD Image A NanoBSD image is built using a simple nanobsd.sh shell script, which can @@ -186,7 +186,7 @@ - Customizing a NanoBSD image + Customizing a NanoBSD Image This is probably the most important and most interesting feature of NanoBSD. This is also @@ -195,7 +195,7 @@ Invocation of the following command will force the nanobsd.sh to read its configuration from - the myconf.nano file located in the current + myconf.nano located in the current directory: &prompt.root; sh nanobsd.sh -c myconf.nano @@ -213,7 +213,7 @@ - Configuration options + Configuration Options With configuration settings, it is possible to configure options passed to both the buildworld @@ -264,14 +264,14 @@ FlashDevice — Defines what type of - media to use. Check the FlashDevice.sub - file for more details. + media to use. Check FlashDevice.sub + for more details. - Custom functions + Custom Functions It is possible to fine-tune NanoBSD using shell functions in @@ -322,7 +322,7 @@ customize_cmd cust_etc_size - Adding packages + Adding Packages Packages can be added to a NanoBSD image using a custom function. The following function will install @@ -339,7 +339,7 @@ customize_cmd install_packages - Configuration file example + Configuration File Example A complete example of a configuration file for building a custom NanoBSD image can be: @@ -414,7 +414,7 @@ customize_cmd cust_nobeastieThe most important difference of this step from the initial NanoBSD installation is that - now instead of using the _.disk.full file + now instead of using _.disk.full (which contains an image of the entire disk), the _.disk.image image is installed (which contains an image of a single system partition).