#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2018-12-08 14:45-0200\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Put one translator per line, in the form NAME <EMAIL>, YEAR1, YEAR2
msgctxt "_"
msgid "translator-credits"
msgstr ""

#. (itstool) path: info/title
#: article.translate.xml:35
msgid "FreeBSD and Solid State Devices"
msgstr ""

#. (itstool) path: affiliation/address
#: article.translate.xml:44
#, no-wrap
msgid "\n"
"	    <email>john@kozubik.com</email>\n"
"	  "
msgstr ""

#. (itstool) path: authorgroup/author
#: article.translate.xml:38
msgid ""
"<personname> <firstname>John</firstname> <surname>Kozubik</surname> </"
"personname> <affiliation> <_:address-1/> </affiliation>"
msgstr ""

#. (itstool) path: info/copyright
#: article.translate.xml:51
msgid ""
"<year>2001</year> <year>2009</year> <holder>The FreeBSD Documentation "
"Project</holder>"
msgstr ""

#. (itstool) path: legalnotice/para
#: article.translate.xml:58
msgid "FreeBSD is a registered trademark of the FreeBSD Foundation."
msgstr ""

#. (itstool) path: legalnotice/para
#: article.translate.xml:60
msgid ""
"Many of the designations used by manufacturers and sellers to distinguish "
"their products are claimed as trademarks. Where those designations appear in "
"this document, and the FreeBSD Project was aware of the trademark claim, the "
"designations have been followed by the <quote>™</quote> or the <quote>®</"
"quote> symbol."
msgstr ""

#. (itstool) path: legalnotice/title
#: article.translate.xml:70
msgid "Copyright"
msgstr ""

#. (itstool) path: legalnotice/para
#: article.translate.xml:72
msgid ""
"Redistribution and use in source (XML DocBook) and 'compiled' forms (XML, "
"HTML, PDF, PostScript, RTF and so forth) with or without modification, are "
"permitted provided that the following conditions are met:"
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:79
msgid ""
"Redistributions of source code (XML DocBook) must retain the above copyright "
"notice, this list of conditions and the following disclaimer as the first "
"lines of this file unmodified."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:85
msgid ""
"Redistributions in compiled form (transformed to other DTDs, converted to "
"PDF, PostScript, RTF and other formats) must reproduce the above copyright "
"notice, this list of conditions and the following disclaimer in the "
"documentation and/or other materials provided with the distribution."
msgstr ""

#. (itstool) path: important/para
#: article.translate.xml:94
msgid ""
"THIS DOCUMENTATION IS PROVIDED BY THE FREEBSD DOCUMENTATION PROJECT \"AS "
"IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, "
"THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR "
"PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FREEBSD DOCUMENTATION PROJECT "
"BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR "
"CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF "
"SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS "
"INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN "
"CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) "
"ARISING IN ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF "
"THE POSSIBILITY OF SUCH DAMAGE."
msgstr ""

#. (itstool) path: info/pubdate
#. (itstool) path: info/releaseinfo
#: article.translate.xml:110 article.translate.xml:112
msgid ""
"$FreeBSD: head/en_US.ISO8859-1/articles/solid-state/article.xml 44923 2014-"
"05-23 17:36:54Z bcr $"
msgstr ""

#. (itstool) path: abstract/para
#: article.translate.xml:115
msgid ""
"This article covers the use of solid state disk devices in FreeBSD to create "
"embedded systems."
msgstr ""

#. (itstool) path: abstract/para
#: article.translate.xml:118
msgid ""
"Embedded systems have the advantage of increased stability due to the lack "
"of integral moving parts (hard drives). Account must be taken, however, for "
"the generally low disk space available in the system and the durability of "
"the storage medium."
msgstr ""

#. (itstool) path: abstract/para
#: article.translate.xml:124
msgid ""
"Specific topics to be covered include the types and attributes of solid "
"state media suitable for disk use in FreeBSD, kernel options that are of "
"interest in such an environment, the <filename>rc.initdiskless</filename> "
"mechanisms that automate the initialization of such systems and the need for "
"read-only filesystems, and building filesystems from scratch. The article "
"will conclude with some general strategies for small and read-only FreeBSD "
"environments."
msgstr ""

#. (itstool) path: sect1/title
#: article.translate.xml:136
msgid "Solid State Disk Devices"
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:138
msgid ""
"The scope of this article will be limited to solid state disk devices made "
"from flash memory. Flash memory is a solid state memory (no moving parts) "
"that is non-volatile (the memory maintains data even after all power sources "
"have been disconnected). Flash memory can withstand tremendous physical "
"shock and is reasonably fast (the flash memory solutions covered in this "
"article are slightly slower than a EIDE hard disk for write operations, and "
"much faster for read operations). One very important aspect of flash memory, "
"the ramifications of which will be discussed later in this article, is that "
"each sector has a limited rewrite capacity. You can only write, erase, and "
"write again to a sector of flash memory a certain number of times before the "
"sector becomes permanently unusable. Although many flash memory products "
"automatically map bad blocks, and although some even distribute write "
"operations evenly throughout the unit, the fact remains that there exists a "
"limit to the amount of writing that can be done to the device. Competitive "
"units have between 1,000,000 and 10,000,000 writes per sector in their "
"specification. This figure varies due to the temperature of the environment."
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:159
msgid ""
"Specifically, we will be discussing ATA compatible compact-flash units, "
"which are quite popular as storage media for digital cameras. Of particular "
"interest is the fact that they pin out directly to the IDE bus and are "
"compatible with the ATA command set. Therefore, with a very simple and low-"
"cost adaptor, these devices can be attached directly to an IDE bus in a "
"computer. Once implemented in this manner, operating systems such as FreeBSD "
"see the device as a normal hard disk (albeit small)."
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:169
msgid ""
"Other solid state disk solutions do exist, but their expense, obscurity, and "
"relative unease of use places them beyond the scope of this article."
msgstr ""

#. (itstool) path: sect1/title
#: article.translate.xml:175
msgid "Kernel Options"
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:177
msgid ""
"A few kernel options are of specific interest to those creating an embedded "
"FreeBSD system."
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:180
msgid ""
"All embedded FreeBSD systems that use flash memory as system disk will be "
"interested in memory disks and memory filesystems. Because of the limited "
"number of writes that can be done to flash memory, the disk and the "
"filesystems on the disk will most likely be mounted read-only. In this "
"environment, filesystems such as <filename>/tmp</filename> and <filename>/"
"var</filename> are mounted as memory filesystems to allow the system to "
"create logs and update counters and temporary files. Memory filesystems are "
"a critical component to a successful solid state FreeBSD implementation."
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:191
msgid ""
"You should make sure the following lines exist in your kernel configuration "
"file:"
msgstr ""

#. (itstool) path: sect1/programlisting
#: article.translate.xml:194
#, no-wrap
msgid ""
"options         MFS             # Memory Filesystem\n"
"options         MD_ROOT         # md device usable as a potential root "
"device\n"
"pseudo-device   md              # memory disk"
msgstr ""

#. (itstool) path: sect1/title
#: article.translate.xml:200
msgid "The <literal>rc</literal> Subsystem and Read-Only Filesystems"
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:203
msgid ""
"The post-boot initialization of an embedded FreeBSD system is controlled by "
"<filename>/etc/rc.initdiskless</filename>."
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:206
msgid ""
"<filename>/etc/rc.d/var</filename> mounts <filename>/var</filename> as a "
"memory filesystem, makes a configurable list of directories in <filename>/"
"var</filename> with the <citerefentry><refentrytitle>mkdir</"
"refentrytitle><manvolnum>1</manvolnum></citerefentry> command, and changes "
"modes on some of those directories. In the execution of <filename>/etc/rc.d/"
"var</filename>, one other <filename>rc.conf</filename> variable comes into "
"play – <literal>varsize</literal>. A <filename>/var</filename> partition is "
"created by <filename>/etc/rc.d/var</filename> based on the value of this "
"variable in <filename>rc.conf</filename>:"
msgstr ""

#. (itstool) path: sect1/programlisting
#: article.translate.xml:218
#, no-wrap
msgid "varsize=8192"
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:220
msgid "Remember that this value is in sectors by default."
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:222
msgid ""
"The fact that <filename>/var</filename> is a read-write filesystem is an "
"important distinction, as the <filename>/</filename> partition (and any "
"other partitions you may have on your flash media) should be mounted read-"
"only. Remember that in <xref linkend=\"intro\"/> we detailed the limitations "
"of flash memory - specifically the limited write capability. The importance "
"of not mounting filesystems on flash media read-write, and the importance of "
"not using a swap file, cannot be overstated. A swap file on a busy system "
"can burn through a piece of flash media in less than one year. Heavy logging "
"or temporary file creation and destruction can do the same. Therefore, in "
"addition to removing the <literal>swap</literal> entry from your <filename>/"
"etc/fstab</filename>, you should also change the Options field for each "
"filesystem to <literal>ro</literal> as follows:"
msgstr ""

#. (itstool) path: sect1/programlisting
#: article.translate.xml:239
#, no-wrap
msgid ""
"# Device                Mountpoint      FStype  Options         Dump    "
"Pass#\n"
"/dev/ad0s1a             /               ufs     ro              1       1"
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:242
msgid ""
"A few applications in the average system will immediately begin to fail as a "
"result of this change. For instance, cron will not run properly as a result "
"of missing cron tabs in the <filename>/var</filename> created by <filename>/"
"etc/rc.d/var</filename>, and syslog and dhcp will encounter problems as well "
"as a result of the read-only filesystem and missing items in the <filename>/"
"var</filename> that <filename>/etc/rc.d/var</filename> has created. These "
"are only temporary problems though, and are addressed, along with solutions "
"to the execution of other common software packages in <xref linkend="
"\"strategies\"/>."
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:254
msgid ""
"An important thing to remember is that a filesystem that was mounted read-"
"only with <filename>/etc/fstab</filename> can be made read-write at any time "
"by issuing the command:"
msgstr ""

#. (itstool) path: sect1/screen
#: article.translate.xml:258
#, no-wrap
msgid ""
"<prompt>#</prompt> <userinput>/sbin/mount -uw <replaceable>partition</"
"replaceable></userinput>"
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:260
msgid "and can be toggled back to read-only with the command:"
msgstr ""

#. (itstool) path: sect1/screen
#: article.translate.xml:263
#, no-wrap
msgid ""
"<prompt>#</prompt> <userinput>/sbin/mount -ur <replaceable>partition</"
"replaceable></userinput>"
msgstr ""

#. (itstool) path: sect1/title
#: article.translate.xml:267
msgid "Building a File System from Scratch"
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:269
msgid ""
"Because ATA compatible compact-flash cards are seen by FreeBSD as normal IDE "
"hard drives, you could theoretically install FreeBSD from the network using "
"the kern and mfsroot floppies or from a CD."
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:274
msgid ""
"However, even a small installation of FreeBSD using normal installation "
"procedures can produce a system in size of greater than 200 megabytes. "
"Because most people will be using smaller flash memory devices (128 "
"megabytes is considered fairly large - 32 or even 16 megabytes is common) an "
"installation using normal mechanisms is not possible—there is simply not "
"enough disk space for even the smallest of conventional installations."
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:283
msgid ""
"The easiest way to overcome this space limitation is to install FreeBSD "
"using conventional means to a normal hard disk. After the installation is "
"complete, pare down the operating system to a size that will fit onto your "
"flash media, then tar the entire filesystem. The following steps will guide "
"you through the process of preparing a piece of flash memory for your tarred "
"filesystem. Remember, because a normal installation is not being performed, "
"operations such as partitioning, labeling, file-system creation, etc. need "
"to be performed by hand. In addition to the kern and mfsroot floppy disks, "
"you will also need to use the fixit floppy."
msgstr ""

#. (itstool) path: step/title
#: article.translate.xml:297
msgid "Partitioning Your Flash Media Device"
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:299
msgid ""
"After booting with the kern and mfsroot floppies, choose <literal>custom</"
"literal> from the installation menu. In the custom installation menu, choose "
"<literal>partition</literal>. In the partition menu, you should delete all "
"existing partitions using <keycap>d</keycap>. After deleting all existing "
"partitions, create a partition using <keycap>c</keycap> and accept the "
"default value for the size of the partition. When asked for the type of the "
"partition, make sure the value is set to <literal>165</literal>. Now write "
"this partition table to the disk by pressing <keycap>w</keycap> (this is a "
"hidden option on this screen). If you are using an ATA compatible compact "
"flash card, you should choose the FreeBSD Boot Manager. Now press <keycap>q</"
"keycap> to quit the partition menu. You will be shown the boot manager menu "
"once more - repeat the choice you made earlier."
msgstr ""

#. (itstool) path: step/title
#: article.translate.xml:319
msgid "Creating Filesystems on Your Flash Memory Device"
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:322
msgid ""
"Exit the custom installation menu, and from the main installation menu "
"choose the <literal>fixit</literal> option. After entering the fixit "
"environment, enter the following command:"
msgstr ""

#. (itstool) path: step/screen
#: article.translate.xml:327
#, no-wrap
msgid "<prompt>#</prompt> <userinput>disklabel -e /dev/ad0c</userinput>"
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:329
msgid ""
"At this point you will have entered the vi editor under the auspices of the "
"disklabel command. Next, you need to add an <literal>a:</literal> line at "
"the end of the file. This <literal>a:</literal> line should look like:"
msgstr ""

#. (itstool) path: step/programlisting
#: article.translate.xml:334
#, no-wrap
msgid "a:      <replaceable>123456</replaceable>  0       4.2BSD  0       0"
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:336
msgid ""
"Where <replaceable>123456</replaceable> is a number that is exactly the same "
"as the number in the existing <literal>c:</literal> entry for size. "
"Basically you are duplicating the existing <literal>c:</literal> line as an "
"<literal>a:</literal> line, making sure that fstype is <literal>4.2BSD</"
"literal>. Save the file and exit."
msgstr ""

#. (itstool) path: step/screen
#: article.translate.xml:343
#, no-wrap
msgid ""
"<prompt>#</prompt> <userinput>disklabel -B -r /dev/ad0c</userinput>\n"
"<prompt>#</prompt> <userinput>newfs /dev/ad0a</userinput>"
msgstr ""

#. (itstool) path: step/title
#: article.translate.xml:348
msgid "Placing Your Filesystem on the Flash Media"
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:350
msgid "Mount the newly prepared flash media:"
msgstr ""

#. (itstool) path: step/screen
#: article.translate.xml:352
#, no-wrap
msgid "<prompt>#</prompt> <userinput>mount /dev/ad0a /flash</userinput>"
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:354
msgid ""
"Bring this machine up on the network so we may transfer our tar file and "
"explode it onto our flash media filesystem. One example of how to do this is:"
""
msgstr ""

#. (itstool) path: step/screen
#: article.translate.xml:358
#, no-wrap
msgid ""
"<prompt>#</prompt> <userinput>ifconfig xl0 192.168.0.10 netmask 255.255.255."
"0</userinput>\n"
"<prompt>#</prompt> <userinput>route add default 192.168.0.1</userinput>"
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:361
msgid ""
"Now that the machine is on the network, transfer your tar file. You may be "
"faced with a bit of a dilemma at this point - if your flash memory part is "
"128 megabytes, for instance, and your tar file is larger than 64 megabytes, "
"you cannot have your tar file on the flash media at the same time as you "
"explode it - you will run out of space. One solution to this problem, if you "
"are using FTP, is to untar the file while it is transferred over FTP. If you "
"perform your transfer in this manner, you will never have the tar file and "
"the tar contents on your disk at the same time:"
msgstr ""

#. (itstool) path: step/screen
#: article.translate.xml:373
#, no-wrap
msgid ""
"<prompt>ftp&gt;</prompt> <userinput>get tarfile.tar \"| tar xvf -\"</"
"userinput>"
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:375
msgid "If your tarfile is gzipped, you can accomplish this as well:"
msgstr ""

#. (itstool) path: step/screen
#: article.translate.xml:378
#, no-wrap
msgid ""
"<prompt>ftp&gt;</prompt> <userinput>get tarfile.tar \"| zcat | tar xvf -\"</"
"userinput>"
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:380
msgid ""
"After the contents of your tarred filesystem are on your flash memory "
"filesystem, you can unmount the flash memory and reboot:"
msgstr ""

#. (itstool) path: step/screen
#: article.translate.xml:384
#, no-wrap
msgid ""
"<prompt>#</prompt> <userinput>cd /</userinput>\n"
"<prompt>#</prompt> <userinput>umount /flash</userinput>\n"
"<prompt>#</prompt> <userinput>exit</userinput>"
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:388
msgid ""
"Assuming that you configured your filesystem correctly when it was built on "
"the normal hard disk (with your filesystems mounted read-only, and with the "
"necessary options compiled into the kernel) you should now be successfully "
"booting your FreeBSD embedded system."
msgstr ""

#. (itstool) path: sect1/title
#: article.translate.xml:398
msgid "System Strategies for Small and Read Only Environments"
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:401
msgid ""
"In <xref linkend=\"ro-fs\"/>, it was pointed out that the <filename>/var</"
"filename> filesystem constructed by <filename>/etc/rc.d/var</filename> and "
"the presence of a read-only root filesystem causes problems with many common "
"software packages used with FreeBSD. In this article, suggestions for "
"successfully running cron, syslog, ports installations, and the Apache web "
"server will be provided."
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:410
msgid "Cron"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:412
msgid ""
"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."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:419
msgid ""
"However, this does not solve the problem of maintaining cron tabs across "
"reboots. When the system reboots, the <filename>/var</filename> filesystem "
"that is in memory will disappear and any cron tabs you may have had in it "
"will also disappear. Therefore, one solution would be to create cron tabs "
"for the users that need them, mount your <filename>/</filename> filesystem "
"as read-write and copy those cron tabs to somewhere safe, like <filename>/"
"etc/tabs</filename>, then add a line to the end of <filename>/etc/rc."
"initdiskless</filename> that copies those crontabs into <filename>/var/cron/"
"tabs</filename> after that directory has been created during system "
"initialization. You may also need to add a line that changes modes and "
"permissions on the directories you create and the files you copy with "
"<filename>/etc/rc.initdiskless</filename>."
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:437
msgid "Syslog"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:439
msgid ""
"<filename>syslog.conf</filename> specifies the locations of certain log "
"files that exist in <filename>/var/log</filename>. These files are not "
"created by <filename>/etc/rc.d/var</filename> upon system initialization. "
"Therefore, somewhere in <filename>/etc/rc.d/var</filename>, after the "
"section that creates the directories in <filename>/var</filename>, you will "
"need to add something like this:"
msgstr ""

#. (itstool) path: sect2/screen
#: article.translate.xml:448
#, no-wrap
msgid ""
"<prompt>#</prompt> <userinput>touch /var/log/security /var/log/maillog /var/"
"log/cron /var/log/messages</userinput>\n"
"<prompt>#</prompt> <userinput>chmod 0644 /var/log/*</userinput>"
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:453
msgid "Ports Installation"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:455
msgid ""
"Before discussing the changes necessary to successfully 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 filesystems read-only when you are "
"done with any maintenance - unnecessary writes to the flash media could "
"considerably shorten its lifespan."
msgstr ""

#. (itstool) path: para/buildtarget
#: article.translate.xml:466 article.translate.xml:489
msgid "install"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:464
msgid ""
"To make it possible to enter a ports directory and successfully run "
"<command>make</command> <_:buildtarget-1/>, 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."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:474
msgid ""
"First, create a package database directory. This is normally in <filename>/"
"var/db/pkg</filename>, but we cannot place it there as it will disappear "
"every time the system is booted."
msgstr ""

#. (itstool) path: sect2/screen
#: article.translate.xml:479
#, no-wrap
msgid "<prompt>#</prompt> <userinput>mkdir /etc/pkg</userinput>"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:481
msgid ""
"Now, add a line to <filename>/etc/rc.d/var</filename> that links the "
"<filename>/etc/pkg</filename> directory to <filename>/var/db/pkg</filename>. "
"An example:"
msgstr ""

#. (itstool) path: sect2/screen
#: article.translate.xml:485
#, no-wrap
msgid "<prompt>#</prompt> <userinput>ln -s /etc/pkg /var/db/pkg</userinput>"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:487
msgid ""
"Now, any time that you mount your filesystems as read-write and install a "
"package, the <command>make</command> <_:buildtarget-1/> 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 <filename>/var/db/"
"pkg</filename>."
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:498
msgid "Apache Web Server"
msgstr ""

#. (itstool) path: note/para
#: article.translate.xml:501
msgid ""
"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>."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:508
msgid ""
"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 <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."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:521
msgid ""
"First, add the directory <literal>log/apache</literal> to the list of "
"directories to be created in <filename>/etc/rc.d/var</filename>."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:525
msgid ""
"Second, add these commands to <filename>/etc/rc.d/var</filename> after the "
"directory creation section:"
msgstr ""

#. (itstool) path: sect2/screen
#: article.translate.xml:529
#, no-wrap
msgid ""
"<prompt>#</prompt> <userinput>chmod 0774 /var/log/apache</userinput>\n"
"<prompt>#</prompt> <userinput>chown nobody:nobody /var/log/apache</"
"userinput>"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:532
msgid ""
"Finally, remove the existing <filename><replaceable>apache_log_dir</"
"replaceable></filename> directory, and replace it with a link:"
msgstr ""

#. (itstool) path: sect2/screen
#: article.translate.xml:536
#, no-wrap
msgid ""
"<prompt>#</prompt> <userinput>rm -rf <replaceable>apache_log_dir</"
"replaceable></userinput>\n"
"<prompt>#</prompt> <userinput>ln -s /var/log/apache "
"<replaceable>apache_log_dir</replaceable></userinput>"
msgstr ""