svn commit: r44920 - head/en_US.ISO8859-1/articles/solid-state
Benedict Reuschling
bcr at FreeBSD.org
Fri May 23 17:12:03 UTC 2014
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$
-->
-<article xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
- <info><title>&os; and Solid State Devices</title>
-
+<article xmlns="http://docbook.org/ns/docbook"
+ xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
+ xml:lang="en"> <info>
+ <title>&os; and Solid State Devices</title>
<authorgroup>
- <author><personname><firstname>John</firstname><surname>Kozubik</surname></personname><affiliation>
- <address><email>john at kozubik.com</email></address>
- </affiliation></author>
+ <author>
+ <personname>
+ <firstname>John</firstname>
+ <surname>Kozubik</surname>
+ </personname>
+ <affiliation>
+ <address>
+ <email>john at kozubik.com</email>
+ </address>
+ </affiliation>
+ </author>
</authorgroup>
<copyright>
@@ -120,10 +129,10 @@
</sect1>
<sect1 xml:id="kernel">
- <title>Kernel Options</title>
+ <title>Kernel Options</title>
- <para>A few kernel options are of specific interest to those
- creating an embedded &os; system.</para>
+ <para>A few kernel options are of specific interest to those
+ creating an embedded &os; system.</para>
<para>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
<screen>&prompt.root; <userinput>/sbin/mount -uw <replaceable>partition</replaceable></userinput></screen>
- <para>and can be toggled back to read-only with the command:</para>
+ <para>and can be toggled back to read-only with the
+ command:</para>
<screen>&prompt.root; <userinput>/sbin/mount -ur <replaceable>partition</replaceable></userinput></screen>
</sect1>
@@ -356,11 +366,12 @@ pseudo-device md # memory
<sect2>
<title>cron</title>
- <para>Upon boot, <filename>/var</filename>
- gets populated by <filename>/etc/rc.d/var</filename> using the
- list from <filename>/etc/mtree/BSD.var.dist</filename>, so the
- <filename>cron</filename>, <filename>cron/tabs</filename>, <filename>at</filename>, and a few other standard
- directories get created.</para>
+ <para>Upon boot, <filename>/var</filename> gets populated by
+ <filename>/etc/rc.d/var</filename> using the list from
+ <filename>/etc/mtree/BSD.var.dist</filename>, so the
+ <filename>cron</filename>, <filename>cron/tabs</filename>,
+ <filename>at</filename>, and a few other standard directories
+ get created.</para>
<para>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 <xref linkend="ro-fs"/>. You should always remount those
+ them read-write using the mount syntax shown in <xref
+ linkend="ro-fs"/>. 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.</para>
<para>To make it possible to enter a ports directory and
- successfully run
- <command>make</command> <buildtarget>install</buildtarget>, 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.</para>
+ successfully run <command>make</command>
+ <buildtarget>install</buildtarget>, 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.</para>
<para>First, create a package database directory. This is
normally in <filename>/var/db/pkg</filename>, but we cannot
@@ -431,9 +443,9 @@ pseudo-device md # memory
<screen>&prompt.root; <userinput>ln -s /etc/pkg /var/db/pkg</userinput></screen>
<para>Now, any time that you mount your filesystems as
- read-write and install a package, the
- <command>make</command> <buildtarget>install</buildtarget> will
- work, and package information will be written successfully to
+ read-write and install a package, the <command>make</command>
+ <buildtarget>install</buildtarget> will work, and package
+ information will be written successfully to
<filename>/etc/pkg</filename> (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
<note>
<para>The steps in this section are only necessary if Apache
is set up to write its pid or log information outside of
- <filename>/var</filename>. By default,
- Apache keeps its pid file in <filename>/var/run/httpd.pid</filename> and its
- log files in <filename>/var/log</filename>.</para>
+ <filename>/var</filename>. By default, Apache keeps its pid
+ file in <filename>/var/run/httpd.pid</filename> and its log
+ files in <filename>/var/log</filename>.</para>
</note>
<para>It is now assumed that Apache keeps its log files in a
- directory <filename><replaceable>apache_log_dir</replaceable></filename>
- outside of <filename>/var</filename>.
- 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 <filename>/etc/rc.d/var</filename> to
- create in <filename>/var</filename>, and to link
+ directory
+ <filename><replaceable>apache_log_dir</replaceable></filename>
+ outside of <filename>/var</filename>. 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 <filename>/etc/rc.d/var</filename> to create in
+ <filename>/var</filename>, and to link
<filename><replaceable>apache_log_dir</replaceable></filename>
to <filename>/var/log/apache</filename>. It is also necessary
to set permissions and ownership on this new directory.</para>
@@ -474,7 +487,8 @@ pseudo-device md # memory
<screen>&prompt.root; <userinput>chmod 0774 /var/log/apache</userinput>
&prompt.root; <userinput>chown nobody:nobody /var/log/apache</userinput></screen>
- <para>Finally, remove the existing <filename><replaceable>apache_log_dir</replaceable></filename>
+ <para>Finally, remove the existing
+ <filename><replaceable>apache_log_dir</replaceable></filename>
directory, and replace it with a link:</para>
<screen>&prompt.root; <userinput>rm -rf <replaceable>apache_log_dir</replaceable></userinput>
More information about the svn-doc-head
mailing list