s/role="directory"/class="directory"/ since the last instance is the
correct one. I'm guilty of most of these wrong attributes.
This commit is contained in:
Marc Fonvieille
parent
0a4f6331b3
commit
5055021668
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=22988
10 changed files with 34 additions and 34 deletions
|
|
@ -352,7 +352,7 @@
|
|||
|
||||
<para>Before the advent of rcNG, applications would drop a
|
||||
simple start up script into the
|
||||
<filename role="directory">/usr/local/etc/rc.d</filename>
|
||||
<filename class="directory">/usr/local/etc/rc.d</filename>
|
||||
directory which would be read by the system initialization
|
||||
scripts. These scripts would then be executed during the latter
|
||||
stages of system start up.</para>
|
||||
|
|
@ -472,7 +472,7 @@ run_rc_command "$1"</programlisting>
|
|||
with the &man.rcorder.8; utility and provide for easier
|
||||
configuration via the <filename>rc.conf</filename> file. In
|
||||
essence, this script could even be placed in
|
||||
<filename role="directory">/etc/rc.d</filename> directory.
|
||||
<filename class="directory">/etc/rc.d</filename> directory.
|
||||
Yet, that has the potential to upset the &man.mergemaster.8;
|
||||
utility when used in conjunction with software upgrades.</para>
|
||||
</sect2>
|
||||
|
|
@ -2589,13 +2589,13 @@ device_probe_and_attach: cbb0 attach returned 12</screen>
|
|||
provided an interpreter (<acronym>ACPI-CA</acronym>) that is
|
||||
shared with Linux and NetBSD. The path to the
|
||||
<acronym>ACPI-CA</acronym> source code is
|
||||
<filename role="directory">src/sys/contrib/dev/acpica</filename>.
|
||||
<filename class="directory">src/sys/contrib/dev/acpica</filename>.
|
||||
The glue code that allows <acronym>ACPI-CA</acronym> to work on
|
||||
&os; is in
|
||||
<filename>src/sys/dev/acpica/Osd</filename>. Finally, drivers
|
||||
that implement various <acronym>ACPI</acronym> devices are found
|
||||
in
|
||||
<filename role="directory">src/sys/dev/acpica</filename>.</para>
|
||||
<filename class="directory">src/sys/dev/acpica</filename>.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="ACPI-comprob">
|
||||
|
|
@ -2878,7 +2878,7 @@ hw.acpi.s4bios: 0</screen>
|
|||
acpi_dsdt_name="/boot/DSDT.aml"</programlisting>
|
||||
|
||||
<para>Be sure to copy your <filename>DSDT.aml</filename> to the
|
||||
<filename role="directory">/boot</filename> directory.</para>
|
||||
<filename class="directory">/boot</filename> directory.</para>
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
||||
|
|
@ -2915,7 +2915,7 @@ acpi_dsdt_name="/boot/DSDT.aml"</programlisting>
|
|||
make ACPI_DEBUG=1</userinput></screen>
|
||||
|
||||
<para>Install <filename>acpi.ko</filename> in
|
||||
<filename role="directory">/boot/kernel</filename> and add your
|
||||
<filename class="directory">/boot/kernel</filename> and add your
|
||||
desired level and layer to <filename>loader.conf</filename>.
|
||||
This example enables debug messages for all
|
||||
<acronym>ACPI-CA</acronym> components and all
|
||||
|
|
|
|||
|
|
@ -1531,7 +1531,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c
|
|||
create an image of the data before the burning process.</para>
|
||||
|
||||
<para>To burn onto a DVD+R or a DVD-R the data from the <filename
|
||||
role="directory">/path/to/data</filename> directory, use the
|
||||
class="directory">/path/to/data</filename> directory, use the
|
||||
following command:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>growisofs -dvd-compat -Z <replaceable>/dev/cd0</replaceable> -J -R <replaceable>/path/to/data</replaceable></userinput></screen>
|
||||
|
|
@ -1582,7 +1582,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c
|
|||
just burn it in the same way as for any image, see the
|
||||
previous section for an example. If you have made the DVD
|
||||
authoring and the result is in, for example, the directory
|
||||
<filename role="directory">/path/to/video</filename>, the
|
||||
<filename class="directory">/path/to/video</filename>, the
|
||||
following command should be used to burn the DVD-Video:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>growisofs -Z <replaceable>/dev/cd0</replaceable> -dvd-video <replaceable>/path/to/video</replaceable></userinput></screen>
|
||||
|
|
|
|||
|
|
@ -3452,9 +3452,9 @@ To change any of these settings later, edit /etc/rc.conf
|
|||
option specifies the default <filename>log</filename> file;
|
||||
however, when <literal>syslogd</literal> is used all log
|
||||
activity will be sent to the system log daemon. The
|
||||
<filename role="directory">/host</filename> directory is used
|
||||
<filename class="directory">/host</filename> directory is used
|
||||
to mount an exported file system from a remote
|
||||
host, while <filename role="directory">/net</filename>
|
||||
host, while <filename class="directory">/net</filename>
|
||||
directory is used to mount an exported file system from an
|
||||
<acronym>IP</acronym> address. The
|
||||
<filename>/etc/amd.map</filename> file defines the default
|
||||
|
|
@ -5030,7 +5030,7 @@ Please press any key to reboot.</screen>
|
|||
<screen>&prompt.root; <userinput>mount /dev/fd0 /mnt</userinput></screen>
|
||||
|
||||
<para>Now that you have the floppy mounted, you must
|
||||
change into the <filename role="directory">/mnt</filename> directory:</para>
|
||||
change into the <filename class="directory">/mnt</filename> directory:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /mnt</userinput></screen>
|
||||
|
||||
|
|
|
|||
|
|
@ -1419,7 +1419,7 @@ test: biba/high</screen>
|
|||
|
||||
<para>This is a summary of the <acronym>MLS</acronym>
|
||||
policy's features. Another approach is to create a master policy
|
||||
file in <filename role="directory">/etc</filename> which
|
||||
file in <filename class="directory">/etc</filename> which
|
||||
specifies the <acronym>MLS</acronym> policy information and to
|
||||
feed that file into the <command>setfmac</command> command. This
|
||||
method will be explained after all policies are covered.</para>
|
||||
|
|
@ -2141,7 +2141,7 @@ XXX
|
|||
<para>Double-check the label policies. Ensure that the
|
||||
policies are set correctly for the user in question, the
|
||||
&xfree86; application, and
|
||||
the <filename role="directory">/dev</filename>
|
||||
the <filename class="directory">/dev</filename>
|
||||
entries.</para>
|
||||
</step>
|
||||
|
||||
|
|
|
|||
|
|
@ -1792,7 +1792,7 @@ sasl_pwcheck_program="/usr/local/sbin/pwcheck"</programlisting>
|
|||
<screen>&prompt.user; <userinput>mail</userinput></screen>
|
||||
|
||||
<para>The contents of the user mailbox in
|
||||
<filename role="directory">/var/mail</filename> are
|
||||
<filename class="directory">/var/mail</filename> are
|
||||
automatically read by the <command>mail</command> utility.
|
||||
Should the mailbox be empty, the utility exits with a
|
||||
message indicating that no mails could be found. Once the
|
||||
|
|
@ -1930,7 +1930,7 @@ EOT</screen>
|
|||
|
||||
<para><application>mutt</application> will automatically read the
|
||||
contents of the user mailbox in <filename
|
||||
role="directory">/var/mail</filename> and display the contents
|
||||
class="directory">/var/mail</filename> and display the contents
|
||||
if applicable. If no mails are found in the user mailbox, then
|
||||
<application>mutt</application> will wait for commands from the
|
||||
user. The example below shows <application>mutt</application>
|
||||
|
|
@ -2041,7 +2041,7 @@ EOT</screen>
|
|||
specific to the task at hand are shown.</para>
|
||||
|
||||
<para>The default directory opened by <application>pine</application>
|
||||
is the <filename role="directory">inbox</filename>. To view the message index, press
|
||||
is the <filename class="directory">inbox</filename>. To view the message index, press
|
||||
<keycap>I</keycap>, or select the <guimenuitem>MESSAGE INDEX</guimenuitem>
|
||||
option as seen below:</para>
|
||||
|
||||
|
|
|
|||
|
|
@ -2446,12 +2446,12 @@ doc/zh_*</screen>
|
|||
Information</ulink> and
|
||||
<ulink url="&url.articles.releng;/release-proc.html">Release
|
||||
Process</ulink> documents.
|
||||
The <filename role="directory">src</filename> tree uses tag names that
|
||||
The <filename class="directory">src</filename> tree uses tag names that
|
||||
start with <literal>RELENG_</literal> tags.
|
||||
The <filename role="directory">ports</filename> and
|
||||
<filename role="directory">doc</filename> trees use tags whose names
|
||||
The <filename class="directory">ports</filename> and
|
||||
<filename class="directory">doc</filename> trees use tags whose names
|
||||
begin with <literal>RELEASE</literal> tags.
|
||||
Finally, the <filename role="directory">www</filename> tree is not
|
||||
Finally, the <filename class="directory">www</filename> tree is not
|
||||
tagged with any special name for releases.</para>
|
||||
|
||||
<variablelist>
|
||||
|
|
|
|||
|
|
@ -1001,7 +1001,7 @@ no adaptors present</screen>
|
|||
|
||||
<listitem>
|
||||
<para>Documentation is not installed with the port and can be
|
||||
found either on the web or under the port's <filename role='directory'>work</filename>
|
||||
found either on the web or under the port's <filename class='directory'>work</filename>
|
||||
directory.</para>
|
||||
</listitem>
|
||||
|
||||
|
|
@ -1724,7 +1724,7 @@ device `snapscan:/dev/pass3' is a AGFA SNAPSCAN 600 flatbed scanner</screen>
|
|||
identify the scanner. If this happens, you will need to edit
|
||||
the backend configuration file and define the scanner device
|
||||
used. The <filename
|
||||
role="directory">/usr/local/etc/sane.d/</filename> directory
|
||||
class="directory">/usr/local/etc/sane.d/</filename> directory
|
||||
contains all backends configuration files. This
|
||||
identification problem does appear with certain USB
|
||||
scanners.</para>
|
||||
|
|
|
|||
|
|
@ -4049,7 +4049,7 @@ zone "10.168.192.in-addr.arpa" in {
|
|||
|
||||
<para>Configuration files for <command>named</command> currently
|
||||
reside in
|
||||
<filename role="directory">/var/named/etc/namedb/</filename> and
|
||||
<filename class="directory">/var/named/etc/namedb/</filename> and
|
||||
will need modification before use. This is where most of the
|
||||
configuration will be performed.</para>
|
||||
|
||||
|
|
@ -4057,13 +4057,13 @@ zone "10.168.192.in-addr.arpa" in {
|
|||
<title>Configuration of a Master Zone</title>
|
||||
|
||||
<para>To configure a master zone visit
|
||||
<filename role="directory">/var/named/etc/namedb/</filename>
|
||||
<filename class="directory">/var/named/etc/namedb/</filename>
|
||||
and run the following command:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>sh make-localhost</userinput></screen>
|
||||
|
||||
<para>If all went well a new file should exist in the
|
||||
<filename role="directory">master</filename> directory. The
|
||||
<filename class="directory">master</filename> directory. The
|
||||
filenames should be <filename>localhost.rev</filename> for
|
||||
the local domain name and <filename>localhost-v6.rev</filename>
|
||||
for <acronym>IPv6</acronym> configurations. As the default
|
||||
|
|
@ -4077,7 +4077,7 @@ zone "10.168.192.in-addr.arpa" in {
|
|||
<para>Configuration for extra domains or sub domains may be
|
||||
done properly by setting them as a slave zone. In most cases,
|
||||
the <filename>master/localhost.rev</filename> could just be
|
||||
copied over into the <filename role="directory">slave</filename>
|
||||
copied over into the <filename class="directory">slave</filename>
|
||||
directory and modified. Once completed, the files need
|
||||
to be properly added in <filename>named.conf</filename> such
|
||||
as in the following configuration for
|
||||
|
|
@ -4256,10 +4256,10 @@ zone "0.168.192.in-addr.arpa" {
|
|||
<listitem>
|
||||
<para>This specifies the default directory hierarchy for
|
||||
the <application>Apache</application> installation. Binaries are stored in the
|
||||
<filename role="directory">bin</filename> and
|
||||
<filename role="directory">sbin</filename> subdirectories
|
||||
<filename class="directory">bin</filename> and
|
||||
<filename class="directory">sbin</filename> subdirectories
|
||||
of the server root, and configuration files are stored in
|
||||
<filename role="directory">etc/apache</filename>.</para>
|
||||
<filename class="directory">etc/apache</filename>.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
|
|
|||
|
|
@ -1395,7 +1395,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
|
|||
<note>
|
||||
<para>A copy of the <filename>if-simple</filename> script
|
||||
can be found in the <filename
|
||||
role="directory">/usr/share/examples/printing</filename>
|
||||
class="directory">/usr/share/examples/printing</filename>
|
||||
directory.</para>
|
||||
</note>
|
||||
</sect4>
|
||||
|
|
@ -1588,7 +1588,7 @@ $%&'()*+,-./01234567
|
|||
<note>
|
||||
<para>A copy of the various scripts described below can be
|
||||
found in the <filename
|
||||
role="directory">/usr/share/examples/printing</filename>
|
||||
class="directory">/usr/share/examples/printing</filename>
|
||||
directory.</para>
|
||||
</note>
|
||||
|
||||
|
|
|
|||
|
|
@ -5851,7 +5851,7 @@ An optional company name []:<userinput><replaceable>Another Name</replaceable></
|
|||
authority signature file, <filename>myca.key</filename> and the
|
||||
certificate itself, <filename>new.crt</filename>. These should
|
||||
be placed in a directory, preferably under
|
||||
<filename role="directory">/etc</filename>, which is readable
|
||||
<filename class="directory">/etc</filename>, which is readable
|
||||
only by <username>root</username>. Permissions of 0700 should be fine for this and
|
||||
they can be set with the <command>chmod</command>
|
||||
utility.</para>
|
||||
|
|
@ -5884,13 +5884,13 @@ define(`confSERVER_CERT',`/etc/certs/new.crt')dnl
|
|||
define(`confSERVER_KEY',`/etc/certs/myca.key')dnl
|
||||
define(`confTLS_SRV_OPTIONS', `V')dnl</programlisting>
|
||||
|
||||
<para>Where <filename role="directory">/etc/certs/</filename>
|
||||
<para>Where <filename class="directory">/etc/certs/</filename>
|
||||
is the directory to be used for storing the certificate
|
||||
and key files locally. The last few requirements are a rebuild
|
||||
of the local <filename>.cf</filename> file. This is easily
|
||||
achieved by typing <command>make</command>
|
||||
<parameter>install</parameter> within the
|
||||
<filename role="directory">/etc/mail</filename>
|
||||
<filename class="directory">/etc/mail</filename>
|
||||
directory. Follow that up with <command>make</command>
|
||||
<parameter>restart</parameter> which should start the
|
||||
<application>Sendmail</application> daemon.</para>
|
||||
|
|
|
|||
Loading…
Reference in a new issue