os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

- Fix role="directory" attributes (replace with class="directory") in

Browse source 
<filename> elements, because there is no such attribute [1]
- Add further missing class="directory" attributes

[1] http://www.freebsd.org/cgi/cvsweb.cgi/doc/en_US.ISO8859-1/books/handbook/printing/chapter.sgml?rev=1.89

Reviewed by:	trhodes, remko, keramida
Approved by:	gabor (mentor)
This commit is contained in:
Gabor Pali 2008-08-06 22:14:51 +00:00
parent edafad6a69
commit 2de9e36d48
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=32633
1 changed files with 57 additions and 57 deletions
Download patch file Download diff file Expand all files Collapse all files

114
en_US.ISO8859-1/books/faq/book.sgml
View file

@ -668,7 +668,7 @@
<listitem>
<para>The document's language and encoding. These are
based on the locale names you will find under
<filename>/usr/share/locale</filename> on your &os;
<filename class="directory">/usr/share/locale</filename> on your &os;
system. The current languages and encodings that we
have for documentation are as follows:</para>
@ -956,7 +956,7 @@
<para>So the &postscript; version of the Handbook,
compressed using BZip2 will be stored in a file
called <filename>book.ps.bz2</filename> in the
<filename>handbook/</filename> directory.</para>
<filename class="directory">handbook/</filename> directory.</para>
</listitem>
</orderedlist>
</listitem>
@ -1333,7 +1333,7 @@
<itemizedlist>
<listitem>
<para>Running DOS, go into the <filename
role="directory">tools</filename> directory of your
class="directory">tools</filename> directory of your
&os; distribution and look for
<filename>bootinst.exe</filename>. You run it like
so:</para>
@ -1710,7 +1710,7 @@
<para>Alternatively, there is a freely available utility
distributed with &os; called
<filename>pfdisk.exe</filename>. You can find it in the
<filename role="directory">tools</filename> subdirectory on
<filename class="directory">tools</filename> subdirectory on
the &os; CD-ROM or on the various &os; FTP sites. This
program can be used to work out what geometry the other
operating systems on the disk are using. You can then enter
@ -1815,7 +1815,7 @@
read-only mount the sources from elsewhere via NFS and still
be able to make new binaries (due to the kernel-source
restriction, we recommend that you not mount this on
<filename role="directory">/usr/src</filename> directly, but
<filename class="directory">/usr/src</filename> directly, but
rather in some other location with appropriate symbolic
links to duplicate the top-level structure of the source
tree).</para>
@ -3793,7 +3793,7 @@ chip1@pci0:31:5: class=0x040100 card=0x00931028 chip=0x24158086 rev=0x02
option <literal>UseDNS</literal> is set to
<literal>yes</literal> by default in the
<filename>sshd_config</filename> file in
<filename>/etc/ssh</filename>. If this is causing the
<filename class="directory">/etc/ssh</filename>. If this is causing the
problem, you will either need to fill in the missing
information in <filename>/etc/resolv.conf</filename> or set
<literal>UseDNS</literal> to <literal>no</literal> in
@ -4363,7 +4363,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
7.<replaceable>X</replaceable> and
8.<replaceable>X</replaceable> branches. Each time a &os;
release is made, a snapshot of the ports tree at the time of
release in also included in the <filename>ports/</filename>
release in also included in the <filename class="directory">ports/</filename>
directory.</para>
<para>We also support the concept of a <quote>package</quote>,
@ -4380,7 +4380,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
you are interested in installing. Package files can usually
be identified by their <filename>.tbz</filename> suffix and
CD-ROM distribution people will have a
<filename>packages/All</filename> directory on their CD
<filename class="directory">packages/All</filename> directory on their CD
which contains such files. They can also be downloaded over
the net for various versions of &os; at the following
locations:</para>
@ -4704,9 +4704,9 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
<note>
<para>The new <filename>kernel</filename> will be installed
to the <filename>/boot/kernel</filename> directory along
to the <filename class="directory">/boot/kernel</filename> directory along
with its modules, while the old kernel and its modules
will be moved to the <filename>/boot/kernel.old</filename>
will be moved to the <filename class="directory">/boot/kernel.old</filename>
directory, so if you make a mistake the next time you play
with your configuration you can boot the previous version
of your kernel.</para>
@ -4950,7 +4950,7 @@ kern.sched.name: 4BSD</screen>
<para>Now you have the new disk set up, and are ready to move
the data. Unfortunately, you cannot just blindly copy the
data. Things like device files (in
<filename>/dev</filename>), flags, and links tend to screw
<filename class="directory">/dev</filename>), flags, and links tend to screw
that up. You need to use tools that understand these
things, which means &man.dump.8;. Although it is suggested
that you move the data in single user mode, it is not
@ -4986,7 +4986,7 @@ kern.sched.name: 4BSD</screen>
<para>For example, if you are going to move root to
<devicename>/dev/<replaceable>ad1s1a</replaceable></devicename>,
with <filename><replaceable>/mnt</replaceable></filename> as
with <filename class="directory"><replaceable>/mnt</replaceable></filename> as
the temporary mount point, it is:</para>
<screen>&prompt.root; <userinput>newfs /dev/<replaceable>ad1s1a</replaceable></userinput>
@ -4996,7 +4996,7 @@ kern.sched.name: 4BSD</screen>
<para>Rearranging your partitions with <command>dump</command>
takes a bit more work. To merge a partition like
<filename>/var</filename> into its parent, create the new
<filename class="directory">/var</filename> into its parent, create the new
partition large enough for both, move the parent partition
as described above, then move the child partition into the
empty directory that the first move created:</para>
@ -5009,7 +5009,7 @@ kern.sched.name: 4BSD</screen>
&prompt.root; <userinput>dump 0af - /var | restore xf -</userinput></screen>
<para>To split a directory from its parent, say putting
<filename>/var</filename> on its own partition when it was
<filename class="directory">/var</filename> on its own partition when it was
not before, create both partitions, then mount the child
partition on the appropriate directory in the temporary
mount point, then move the old single partition:</para>
@ -5139,7 +5139,7 @@ kern.sched.name: 4BSD</screen>
<qandaentry>
<question id="safe-softupdates">
<para>Which partitions can safely use Soft Updates? I have
heard that Soft Updates on <filename>/</filename> can cause
heard that Soft Updates on <filename class="directory">/</filename> can cause
problems.</para>
</question>
@ -5185,7 +5185,7 @@ kern.sched.name: 4BSD</screen>
<para>Vital information on the root partition changes very
rarely. Files such as
<filename>/boot/kernel/kernel</filename> and the contents of
<filename>/etc</filename> only change during system
<filename class="directory">/etc</filename> only change during system
maintenance, or when users change their passwords. If the
system crashed during the thirty-second window after such a
change is made, it is possible that data could be lost.
@ -5194,13 +5194,13 @@ kern.sched.name: 4BSD</screen>
tolerate this much risk, do not use Soft Updates on the root
file system!</para>
<para><filename>/</filename> is traditionally one of the
<para><filename class="directory">/</filename> is traditionally one of the
smallest partitions. If you put the
<filename>/tmp</filename> directory on
<filename>/</filename> and you have a busy
<filename>/tmp</filename>, you might see intermittent space
problems. Symlinking <filename>/tmp</filename> to
<filename>/var/tmp</filename> will solve this
<filename class="directory">/tmp</filename> directory on
<filename class="directory">/</filename> and you have a busy
<filename class="directory">/tmp</filename>, you might see intermittent space
problems. Symlinking <filename class="directory">/tmp</filename> to
<filename class="directory">/var/tmp</filename> will solve this
problem.</para>
</answer>
</qandaentry>
@ -5348,7 +5348,7 @@ use "disklabel -r" to install initial label</screen>
example, if you have an <quote>E</quote> partition as the
second DOS partition on the second SCSI drive, there will be
a device file for <quote>slice 5</quote> in
<filename>/dev</filename>, so simply mount it:</para>
<filename class="directory">/dev</filename>, so simply mount it:</para>
<screen>&prompt.root; <userinput>mount -t msdos /dev/da1s5 /dos/e</userinput></screen>
</answer>
@ -5528,7 +5528,7 @@ C:\="DOS"</programlisting>
<answer>
<para>You can not do that with the standard boot manager
without rewriting it. There are a number of other boot
managers in the <filename>sysutils</filename> ports category
managers in the <filename class="directory">sysutils</filename> ports category
that provide this functionality.</para>
</answer>
</qandaentry>
@ -5862,7 +5862,7 @@ perm /dev/acd0 0660</programlisting>
<para>This situation is common on web servers. Many people
set up a &os; web server and forget to rotate the log files.
The access log fills up <filename>/var</filename>. The new
The access log fills up <filename class="directory">/var</filename>. The new
administrator deletes the file, but the system still
complains that the partition is full. Stopping and
restarting the web server program would free the file,
@ -5942,8 +5942,8 @@ perm /dev/acd0 0660</programlisting>
<para>The primary configuration file is
<filename>/etc/defaults/rc.conf</filename> (see
&man.rc.conf.5;). System startup scripts such as
<filename>/etc/rc</filename> and
<filename>/etc/rc.d</filename> (see &man.rc.8;) just include
<filename class="directory">/etc/rc</filename> and
<filename class="directory">/etc/rc.d</filename> (see &man.rc.8;) just include
this file. <emphasis>Do not edit this file!</emphasis>
Instead, if there is any entry in
<filename>/etc/defaults/rc.conf</filename> that you want to
@ -5957,7 +5957,7 @@ perm /dev/acd0 0660</programlisting>
<screen>&prompt.root; <userinput>echo named_enable="YES" &gt;&gt; /etc/rc.conf</userinput></screen>
<para>To start up local services, place shell scripts in the
<filename>/usr/local/etc/rc.d</filename> directory. These
<filename class="directory">/usr/local/etc/rc.d</filename> directory. These
shell scripts should be set executable, the default file
mode is <literal>555</literal>.</para>
</answer>
@ -6009,7 +6009,7 @@ perm /dev/acd0 0660</programlisting>
<para>If you want something to be run once per day, week, or
month, it is probably better to add shell scripts
<filename>/usr/local/etc/periodic</filename>, and let the
<filename class="directory">/usr/local/etc/periodic</filename>, and let the
&man.periodic.8; command run from the system
<command>cron</command> schedule it with the other periodic
system tasks.</para>
@ -6173,7 +6173,7 @@ perm /dev/acd0 0660</programlisting>
<listitem>
<para>Do not turn on quotas on
<filename>/</filename>.</para>
<filename class="directory">/</filename>.</para>
</listitem>
<listitem>
@ -6192,13 +6192,13 @@ perm /dev/acd0 0660</programlisting>
<tbody>
<row>
<entry><filename>/usr</filename></entry>
<entry><filename class="directory">/usr</filename></entry>
<entry><filename>/usr/admin/quotas</filename></entry>
</row>
<row>
<entry><filename>/home</filename></entry>
<entry><filename class="directory">/home</filename></entry>
<entry><filename>/home/admin/quotas</filename></entry>
</row>
@ -6408,7 +6408,7 @@ options SYSVMSG # enable for messaging</programlisting>
system, reinstall the <literal>base</literal> distribution
for the release you are running. If you have the CD-ROM,
you can mount the it (we will assume on <filename
role="directory">/cdrom</filename>) and run the commands
class="directory">/cdrom</filename>) and run the commands
below:</para>
<screen>&prompt.root; <userinput>cd /cdrom/base</userinput>
@ -6606,7 +6606,7 @@ options SYSVMSG # enable for messaging</programlisting>
off things like &man.top.1; and &man.ps.1;.</para>
<para>&man.rpc.statd.8; maps its status file (resident on
<filename>/var</filename>) into its address space; to save
<filename class="directory">/var</filename>) into its address space; to save
worrying about remapping it later when it needs to grow, it
maps it with a generous size. This is very evident from the
source code, where one can see that the length argument to
@ -6779,14 +6779,14 @@ options SYSVMSG # enable for messaging</programlisting>
<qandaentry>
<question id="var-empty">
<para>What is <filename>/var/empty</filename>? I can not
<para>What is <filename class="directory">/var/empty</filename>? I can not
delete it!</para>
</question>
<answer>
<para><filename>/var/empty</filename> is a directory that the
<para><filename class="directory">/var/empty</filename> is a directory that the
&man.sshd.8; program uses when performing privilege separation.
The <filename>/var/empty</filename> directory is empty, owned by
The <filename class="directory">/var/empty</filename> directory is empty, owned by
<username>root</username> and has the <literal>schg</literal>
flag set.</para>
@ -7213,7 +7213,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
<command>xdm</command> from from
<filename>rc.local</filename> (see &man.rc.8;) or from an
<filename>X</filename> script in
<filename>/usr/local/etc/rc.d</filename>. Both are equally
<filename class="directory">/usr/local/etc/rc.d</filename>. Both are equally
valid, and one may work in situations where the other does
not. In both cases the result is the same: X will pop up a
graphical login prompt.</para>
@ -8344,9 +8344,9 @@ Key F15 A A Menu Workplace Nop</programlisting>
<para>The most common way to accomplish this is to build a
simulated environment in a subdirectory and then run the
processes in that directory chroot'd (i.e. <filename
role="directory">/</filename> for that process is this
class="directory">/</filename> for that process is this
directory, not the real <filename
role="directory">/</filename> of the system).</para>
class="directory">/</filename> of the system).</para>
<para>Another common use is to mount an underlying file
system read-only and then create a file system layer on
@ -8533,12 +8533,12 @@ Key F15 A A Menu Workplace Nop</programlisting>
important as shells which are not part of the base
distribution (for example a shell installed from ports or
packages) are likely to be installed in
<filename>/usr/local/bin</filename> which, by default,
<filename class="directory">/usr/local/bin</filename> which, by default,
resides on a different file system. If
<username>root</username>'s shell is located in
<filename>/usr/local/bin</filename> and
<filename>/usr</filename> (or whatever file system contains
<filename>/usr/local/bin</filename>) is not mounted for some
<filename class="directory">/usr/local/bin</filename> and
<filename class="directory">/usr</filename> (or whatever file system contains
<filename class="directory">/usr/local/bin</filename>) is not mounted for some
reason, <username>root</username> will not be able to log in
to fix a problem (although if you reboot into single user
mode you will be prompted for the path to a shell).</para>
@ -9287,7 +9287,7 @@ ATDT1234567</programlisting>
section), then you should install the system sources and do
the following:</para>
<screen>&prompt.root; <userinput><command>cd</command> <filename role="directory">/usr/src/usr.sbin/ppp</filename></userinput>
<screen>&prompt.root; <userinput><command>cd</command> <filename class="directory">/usr/src/usr.sbin/ppp</filename></userinput>
&prompt.root; <userinput><command>echo</command> <makevar>STRIP</makevar>= &gt;&gt; <filename>/etc/make.conf</filename></userinput>
&prompt.root; <userinput><command>echo</command> <makevar>CFLAGS</makevar>+=<option>-g</option> &gt;&gt; <filename>/etc/make.conf</filename></userinput>
&prompt.root; <userinput><command>make</command> <maketarget>install</maketarget> <maketarget>clean</maketarget></userinput></screen>
@ -9900,7 +9900,7 @@ hint.sio.7.irq="12"</programlisting>
<answer>
<para>On your system, the programs &man.tip.1; and &man.cu.1;
can only access the <filename>/var/spool/lock</filename>
can only access the <filename class="directory">/var/spool/lock</filename>
directory via user <username>uucp</username> and group
<groupname>dialer</groupname>. You can use the group
<groupname>dialer</groupname> to control who has access to
@ -10140,11 +10140,11 @@ hint.sio.7.irq="12"</programlisting>
&man.chmod.1;. If you want to change the permissions of a
directory referenced by a symlink, use &man.chmod.1;
without any options and follow the symlink with a trailing
slash (<filename>/</filename>). For example, if
slash (<filename class="directory">/</filename>). For example, if
<filename>foo</filename> is a symlink to directory
<filename>bar</filename>, and you want to change the
<filename class="directory">bar</filename>, and you want to change the
permissions of <filename>foo</filename> (actually
<filename>bar</filename>), you would do something
<filename class="directory">bar</filename>), you would do something
like:</para>
<screen>&prompt.user; <userinput>chmod 555 foo/</userinput></screen>
@ -10152,7 +10152,7 @@ hint.sio.7.irq="12"</programlisting>
<para>With the trailing slash, &man.chmod.1; will follow the
symlink, <filename>foo</filename>, to change the
permissions of the directory,
<filename>bar</filename>.</para>
<filename class="directory">bar</filename>.</para>
</warning>
</answer>
</qandaentry>
@ -10367,7 +10367,7 @@ hint.sio.7.irq="12"</programlisting>
<answer>
<para>You will find eps and Xfig drawings under
<filename>/usr/share/examples/BSD_daemon/</filename>.</para>
<filename class="directory">/usr/share/examples/BSD_daemon/</filename>.</para>
</answer>
</qandaentry>
@ -10677,7 +10677,7 @@ hint.sio.7.irq="12"</programlisting>
CPU by reading data out of <filename>/dev/random</filename>
and sending it off somewhere; however you run the risk of
overheating your network connection and
<filename>/</filename> or angering your ISP, as most of the
<filename class="directory">/</filename> or angering your ISP, as most of the
data will end up getting converted to heat by their
equipment, but they generally have good cooling, so if you
do not overdo it you should be OK.</para>
@ -11137,10 +11137,10 @@ panic: page fault</programlisting>
<step>
<para>Change to the <filename
role="directory">/usr/src</filename>
class="directory">/usr/src</filename>
directory:</para>
<screen>&prompt.root; <command>cd</command> <filename role="directory">/usr/src</filename></screen>
<screen>&prompt.root; <command>cd</command> <filename class="directory">/usr/src</filename></screen>
</step>
<step>
@ -11187,14 +11187,14 @@ panic: page fault</programlisting>
using &man.savecore.8;; if <literal>dumpdev</literal> is set
in <filename>/etc/rc.conf</filename>, the &man.rc.8; scripts
will run &man.savecore.8; automatically and put the crash
dump in <filename>/var/crash</filename>.</para>
dump in <filename class="directory">/var/crash</filename>.</para>
<note>
<para>&os; crash dumps are usually the same size as the
physical RAM size of your machine. That is, if you have
512&nbsp;MB of RAM, you will get a 512&nbsp;MB crash dump.
Therefore you must make sure there is enough space in
<filename>/var/crash</filename> to hold the dump.
<filename class="directory">/var/crash</filename> to hold the dump.
Alternatively, you run &man.savecore.8; manually and have
it recover the crash dump to another directory where you
have more room. It is possible to limit the size of the
@ -11210,7 +11210,7 @@ panic: page fault</programlisting>
<para>Once you have recovered the crash dump, you can get a
stack trace with &man.kgdb.1; as follows:</para>
<screen>&prompt.user; <userinput><command>kgdb</command> <filename>/usr/obj/usr/src/sys/<replaceable>MYKERNEL</replaceable>/kernel.debug</filename> <filename>/var/crash/<replaceable>vmcore.0</replaceable></filename></userinput>
<screen>&prompt.user; <userinput><command>kgdb</command> <filename>/usr/obj/usr/src/sys/<replaceable>MYKERNEL</replaceable>/kernel.debug</filename> <filename class="directory">/var/crash/<replaceable>vmcore.0</replaceable></filename></userinput>
<prompt>(kgdb)</prompt> <userinput>backtrace</userinput></screen>
<para>Note that there may be several screens worth of