From owner-svn-doc-head@FreeBSD.ORG Fri May 23 17:12:03 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B756B763; Fri, 23 May 2014 17:12:03 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 982D622BB; Fri, 23 May 2014 17:12:03 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s4NHC3IM047324; Fri, 23 May 2014 17:12:03 GMT (envelope-from bcr@svn.freebsd.org) Received: (from bcr@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s4NHC3um047323; Fri, 23 May 2014 17:12:03 GMT (envelope-from bcr@svn.freebsd.org) Message-Id: <201405231712.s4NHC3um047323@svn.freebsd.org> From: Benedict Reuschling Date: Fri, 23 May 2014 17:12:03 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44920 - head/en_US.ISO8859-1/articles/solid-state X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.18 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, 23 May 2014 17:12:03 -0000 Author: bcr Date: Fri May 23 17:12:03 2014 New Revision: 44920 URL: http://svnweb.freebsd.org/changeset/doc/44920 Log: Whitespace fixes to the whole article based on output by igor. Modified: head/en_US.ISO8859-1/articles/solid-state/article.xml Modified: head/en_US.ISO8859-1/articles/solid-state/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/solid-state/article.xml Fri May 23 16:49:32 2014 (r44919) +++ head/en_US.ISO8859-1/articles/solid-state/article.xml Fri May 23 17:12:03 2014 (r44920) @@ -32,14 +32,23 @@ $FreeBSD$ --> -
- &os; and Solid State Devices - +
+ &os; and Solid State Devices - JohnKozubik -
john@kozubik.com
- + + + John + Kozubik + + +
+ john@kozubik.com +
+ + @@ -120,10 +129,10 @@ - Kernel Options + Kernel Options - A few kernel options are of specific interest to those - creating an embedded &os; system. + A few kernel options are of specific interest to those + creating an embedded &os; system. All embedded &os; systems that use flash memory as system disk will be interested in memory disks and memory filesystems. @@ -205,7 +214,8 @@ pseudo-device md # memory &prompt.root; /sbin/mount -uw partition - and can be toggled back to read-only with the command: + and can be toggled back to read-only with the + command: &prompt.root; /sbin/mount -ur partition @@ -356,11 +366,12 @@ pseudo-device md # memory cron - Upon boot, /var - gets populated by /etc/rc.d/var using the - list from /etc/mtree/BSD.var.dist, so the - cron, cron/tabs, at, and a few other standard - directories get created. + Upon boot, /var gets populated by + /etc/rc.d/var using the list from + /etc/mtree/BSD.var.dist, so the + cron, cron/tabs, + at, and a few other standard directories + get created. However, this does not solve the problem of maintaining cron tabs across reboots. When the system reboots, the @@ -402,20 +413,21 @@ pseudo-device md # memory use the ports tree, a reminder is necessary regarding the read-only nature of your filesystems on the flash media. Since they are read-only, you will need to temporarily mount - them read-write using the mount syntax shown in . You should always remount those + them read-write using the mount syntax shown in . You should always remount those filesystems read-only when you are done with any maintenance - unnecessary writes to the flash media could considerably shorten its lifespan. To make it possible to enter a ports directory and - successfully run - make install, we - must create a packages directory on a non-memory filesystem - that will keep track of our packages across reboots. Because - it is necessary to mount your filesystems as read-write for - the installation of a package anyway, it is sensible to assume - that an area on the flash media can also be used for package - information to be written to. + successfully run make + install, we must create a packages + directory on a non-memory filesystem that will keep track of + our packages across reboots. Because it is necessary to mount + your filesystems as read-write for the installation of a + package anyway, it is sensible to assume that an area on the + flash media can also be used for package information to be + written to. First, create a package database directory. This is normally in /var/db/pkg, but we cannot @@ -431,9 +443,9 @@ pseudo-device md # memory &prompt.root; ln -s /etc/pkg /var/db/pkg Now, any time that you mount your filesystems as - read-write and install a package, the - make install will - work, and package information will be written successfully to + read-write and install a package, the make + install will work, and package + information will be written successfully to /etc/pkg (because the filesystem will, at that time, be mounted read-write) which will always be available to the operating system as @@ -446,19 +458,20 @@ pseudo-device md # memory The steps in this section are only necessary if Apache is set up to write its pid or log information outside of - /var. By default, - Apache keeps its pid file in /var/run/httpd.pid and its - log files in /var/log. + /var. By default, Apache keeps its pid + file in /var/run/httpd.pid and its log + files in /var/log. It is now assumed that Apache keeps its log files in a - directory apache_log_dir - outside of /var. - When this directory lives on a read-only filesystem, Apache - will not be able to save any log files, and may have problems - working. If so, it is necessary to add a new directory to the - list of directories in /etc/rc.d/var to - create in /var, and to link + directory + apache_log_dir + outside of /var. When this directory + lives on a read-only filesystem, Apache will not be able to + save any log files, and may have problems working. If so, it + is necessary to add a new directory to the list of directories + in /etc/rc.d/var to create in + /var, and to link apache_log_dir to /var/log/apache. It is also necessary to set permissions and ownership on this new directory. @@ -474,7 +487,8 @@ pseudo-device md # memory &prompt.root; chmod 0774 /var/log/apache &prompt.root; chown nobody:nobody /var/log/apache - Finally, remove the existing apache_log_dir + Finally, remove the existing + apache_log_dir directory, and replace it with a link: &prompt.root; rm -rf apache_log_dir