diff options
Diffstat (limited to 'en_US.ISO8859-1/articles/solid-state/article.xml')
| -rw-r--r-- | en_US.ISO8859-1/articles/solid-state/article.xml | 78 |
1 files changed, 31 insertions, 47 deletions
diff --git a/en_US.ISO8859-1/articles/solid-state/article.xml b/en_US.ISO8859-1/articles/solid-state/article.xml index 1290cb19cc..b47dd45d06 100644 --- a/en_US.ISO8859-1/articles/solid-state/article.xml +++ b/en_US.ISO8859-1/articles/solid-state/article.xml @@ -1,7 +1,6 @@ <?xml version="1.0" encoding="iso-8859-1"?> -<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.5-Based Extension//EN" - "../../../share/xml/freebsd45.dtd"> - +<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN" + "../../../share/xml/freebsd50.dtd"> <!-- Copyright (c) 2001 The FreeBSD Documentation Project Redistribution and use in source (SGML DocBook) and 'compiled' forms @@ -33,20 +32,14 @@ $FreeBSD$ --> - -<article lang='en'> - <articleinfo> - <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> - <firstname>John</firstname> - <surname>Kozubik</surname> - - <affiliation> + <author><personname><firstname>John</firstname><surname>Kozubik</surname></personname><affiliation> <address><email>john@kozubik.com</email></address> - </affiliation> - </author> + </affiliation></author> </authorgroup> <copyright> @@ -55,7 +48,7 @@ <holder>The FreeBSD Documentation Project</holder> </copyright> - <legalnotice id="trademarks" role="trademarks"> + <legalnotice xml:id="trademarks" role="trademarks"> &tm-attrib.freebsd; &tm-attrib.general; </legalnotice> @@ -85,9 +78,9 @@ The article will conclude with some general strategies for small and read-only &os; environments.</para> </abstract> - </articleinfo> + </info> - <sect1 id="intro"> + <sect1 xml:id="intro"> <title>Solid State Disk Devices</title> <para>The scope of this article will be limited to solid state @@ -126,7 +119,7 @@ beyond the scope of this article.</para> </sect1> - <sect1 id="kernel"> + <sect1 xml:id="kernel"> <title>Kernel Options</title> <para>A few kernel options are of specific interest to those @@ -151,7 +144,7 @@ options MD_ROOT # md device usable as a potential root device pseudo-device md # memory disk</programlisting> </sect1> - <sect1 id="ro-fs"> + <sect1 xml:id="ro-fs"> <title>The <literal>rc</literal> Subsystem and Read-Only Filesystems</title> @@ -210,11 +203,11 @@ pseudo-device md # memory disk</programlisting> mounted read-only with <filename>/etc/fstab</filename> can be made read-write at any time by issuing the command:</para> - <screen>&prompt.root; <userinput>/sbin/mount -uw <replaceable>partition</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>/sbin/mount -uw partition</userinput></screen> <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> + <screen>&prompt.root; <userinput>/sbin/mount -ur partition</userinput></screen> </sect1> <sect1> @@ -324,12 +317,12 @@ pseudo-device md # memory disk</programlisting> have the tar file and the tar contents on your disk at the same time:</para> - <screen><prompt>ftp></prompt> <userinput>get tarfile.tar "| tar xvf -"</userinput></screen> + <screen><prompt>ftp></prompt> <userinput>get tarfile.tar "| tar xvf -"</userinput></screen> <para>If your tarfile is gzipped, you can accomplish this as well:</para> - <screen><prompt>ftp></prompt> <userinput>get tarfile.tar "| zcat | tar xvf -"</userinput></screen> + <screen><prompt>ftp></prompt> <userinput>get tarfile.tar "| zcat | tar xvf -"</userinput></screen> <para>After the contents of your tarred filesystem are on your flash memory filesystem, you can unmount the flash memory @@ -348,7 +341,7 @@ pseudo-device md # memory disk</programlisting> </procedure> </sect1> - <sect1 id="strategies"> + <sect1 xml:id="strategies"> <title>System Strategies for Small and Read Only Environments</title> @@ -363,12 +356,10 @@ pseudo-device md # memory disk</programlisting> <sect2> <title>cron</title> - <para>Upon boot, <filename class="directory">/var</filename> + <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 class="directory">cron</filename>, <filename - class="directory">cron/tabs</filename>, <filename - class="directory">at</filename>, and a few other standard + <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 @@ -411,15 +402,14 @@ pseudo-device md # memory disk</programlisting> 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> <maketarget>install</maketarget>, we + <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 @@ -442,7 +432,7 @@ pseudo-device md # memory disk</programlisting> <para>Now, any time that you mount your filesystems as read-write and install a package, the - <command>make</command> <maketarget>install</maketarget> will + <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 @@ -456,24 +446,20 @@ pseudo-device md # memory disk</programlisting> <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 class="directory">/var</filename>. By default, - Apache keeps its pid file in <filename - class="directory">/var/run/httpd.pid</filename> and its - log files in <filename - class="directory">/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 - class="directory"><replaceable>apache_log_dir</replaceable></filename> - outside of <filename class="directory">/var</filename>. + directory <filename>apache_log_dir</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 - class="directory"><replaceable>apache_log_dir</replaceable></filename> + <filename>apache_log_dir</filename> to <filename>/var/log/apache</filename>. It is also necessary to set permissions and ownership on this new directory.</para> @@ -488,13 +474,11 @@ pseudo-device md # memory disk</programlisting> <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 - class="directory"><replaceable>apache_log_dir</replaceable></filename> + <para>Finally, remove the existing <filename>apache_log_dir</filename> directory, and replace it with a link:</para> - <screen>&prompt.root; <userinput>rm -rf <filename class="directory"><replaceable>apache_log_dir</replaceable></filename></userinput> -&prompt.root; <userinput>ln -s /var/log/apache <filename class="directory"><replaceable>apache_log_dir</replaceable></filename></userinput></screen> + <screen>&prompt.root; <userinput>rm -rf apache_log_dir</userinput> +&prompt.root; <userinput>ln -s /var/log/apache apache_log_dir</userinput></screen> </sect2> </sect1> </article> - |