Mark directory paths with class="directory" in <filename> elements.

Approved by:	gjb (mentor)

en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml

@@ -1274,7 +1274,7 @@ ifconfig_wlan0="WPA DHCP"</programlisting>
 
 	    <para>Then we can bring up the interface:</para>
 
-	    <screen>&prompt.root; <userinput><filename>service netif</filename> start</userinput>
+	    <screen>&prompt.root; <userinput>service netif start</userinput>
 Starting wpa_supplicant.
 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
@@ -2189,8 +2189,8 @@ freebsdap       00:11:95:c3:0d:ac    1   54M 22:1   100 EPS</screen>
 	    can enable debugging messages in the 802.11 protocol
 	    support layer using the <command>wlandebug</command>
 	    program found in
-	    <filename>/usr/src/tools/tools/net80211</filename>.  For
-	    example:</para>
+	    <filename class="directory">/usr/src/tools/tools/net80211</filename>.
+	    For example:</para>
 
 	  <screen>&prompt.root; <userinput>wlandebug -i <replaceable>ath0</replaceable> +scan+auth+debug+assoc</userinput>
   net.wlan.0.debug: 0 =&gt; 0xc80000&lt;assoc,auth,scan&gt;</screen>
@@ -2760,7 +2760,8 @@ Success, response: OK, Success (0x20)</screen>
       <para>In order to provide OBEX Object Push service, &man.sdpd.8;
 	server must be running.  A root folder, where all incoming
 	objects will be stored, must be created.  The default path to
-	the root folder is <filename>/var/spool/obex</filename>.
+	the root folder
+	is <filename class="directory">/var/spool/obex</filename>.
 	Finally, start OBEX server on valid RFCOMM channel number.
 	The OBEX server will automatically register OBEX Object Push
 	service with the local SDP daemon.  The example below shows
@@ -3689,9 +3690,9 @@ ifconfig_<literal>lagg<replaceable>0</replaceable></literal>="laggproto failover
       </listitem>
 
       <listitem>
-	<para>Standard system startup files exist in
-	  <filename>/etc</filename> to detect and support a diskless
-	  system startup.</para>
+	<para>Standard system startup files exist
+	  in <filename class="directory">/etc</filename>
+	  to detect and support a diskless system startup.</para>
       </listitem>
 
       <listitem>
@@ -3710,8 +3711,9 @@ ifconfig_<literal>lagg<replaceable>0</replaceable></literal>="laggproto failover
     <itemizedlist>
       <listitem>
 	<para>The diskless workstations use a shared read-only
-	  <filename>/</filename> file system, and a shared
-	  read-only <filename>/usr</filename>.</para>
+	  <filename class="directory">/</filename> file system,
+	  and a shared read-only
+	  <filename class="directory">/usr</filename>.</para>
 
 	<para>The root file system is a copy of a standard FreeBSD
 	  root (typically the server's), with some configuration files
@@ -4034,8 +4036,9 @@ margaux:ha=0123456789ab:tc=.def100</programlisting>
 	<para>To make a boot floppy, insert a floppy in the drive on
 	  the machine where you installed
 	  <application>Etherboot</application>, then change your
-	  current directory to the <filename>src</filename> directory
-	  in the <application>Etherboot</application> tree and
+	  current directory to
+	  the <filename class="directory">src</filename>
+	  directory in the <application>Etherboot</application> tree and
 	  type:</para>
 
 	<screen>&prompt.root; <userinput>gmake bin32/<replaceable>devicetype</replaceable>.fd0</userinput></screen>
@@ -4093,7 +4096,7 @@ margaux:ha=0123456789ab:tc=.def100</programlisting>
 	  <step>
 	    <para>Create a directory from which
 	      <application>tftpd</application> will serve the files,
-	      e.g., <filename>/tftpboot</filename>.</para>
+	      e.g., <filename class="directory">/tftpboot</filename>.</para>
 	  </step>
 
 	  <step>
@@ -4123,7 +4126,8 @@ margaux:ha=0123456789ab:tc=.def100</programlisting>
 	  </step>
 	</procedure>
 
-	<para>You can place the <filename>tftpboot</filename>
+	<para>You can place
+	  the <filename class="directory">tftpboot</filename>
 	  directory anywhere on the server.  Make sure that the
 	  location is set in both <filename>inetd.conf</filename> and
 	  <filename>dhcpd.conf</filename>.</para>
@@ -4286,7 +4290,7 @@ cd /usr/src/etc; make distribution</programlisting>
 
 	<sect4>
 	  <title>Running with a Read-only
-	    <filename>/usr</filename></title>
+	    <filename class="directory">/usr</filename></title>
 
 	  <indexterm>
 	    <primary>diskless operation</primary>
@@ -4296,7 +4300,8 @@ cd /usr/src/etc; make distribution</programlisting>
 	  <para>If the diskless workstation is configured to run X,
 	    you will have to adjust the
 	    <application>XDM</application> configuration file, which
-	    puts the error log on <filename>/usr</filename> by
+	    puts the error log
+	    on <filename class="directory">/usr</filename> by
 	    default.</para>
 	</sect4>
 
@@ -4310,7 +4315,8 @@ cd /usr/src/etc; make distribution</programlisting>
 	    <command>cpio</command>.</para>
 
 	  <para>In this situation, there are sometimes problems with
-	    the special files in <filename>/dev</filename>, due to
+	    the special files
+	    in <filename class="directory">/dev</filename>, due to
 	    differing major/minor integer sizes.  A solution to this
 	    problem is to export a directory from the non-FreeBSD
 	    server, mount this directory onto a FreeBSD machine, and
@@ -4370,7 +4376,7 @@ cd /usr/src/etc; make distribution</programlisting>
 	  <para>Choose a directory which will have a &os;
 	    installation which will be NFS mountable.  For example, a
 	    directory such as
-	    <filename>/b/tftpboot/FreeBSD/install</filename> can be
+	    <filename class="directory">/b/tftpboot/FreeBSD/install</filename> can be
 	    used.</para>
 
 	  <screen>&prompt.root; <userinput>export NFSROOTDIR=/b/tftpboot/FreeBSD/install</userinput>
@@ -4500,8 +4506,10 @@ myhost.example.com:/b/tftpboot/FreeBSD/install       /         nfs      ro
 	<filename>/etc/rc</filename> detects that you booted over NFS
 	and runs the <filename>/etc/rc.initdiskless</filename> script.
 	Read the comments in this script to understand what is going
-	on.  We need to make <filename>/etc</filename> and
-	<filename>/var</filename> memory backed file systems because
+	on.  We need to
+	make <filename class="directory">/etc</filename>
+	and <filename class="directory">/var</filename>
+	memory backed file systems because
 	these directories need to be writable, but the NFS root
 	directory is read-only.</para>
 
@@ -4510,8 +4518,9 @@ myhost.example.com:/b/tftpboot/FreeBSD/install       /         nfs      ro
 &prompt.root; <userinput>tar -c -v -f conf/base/etc.cpio.gz --format cpio --gzip etc</userinput>
 &prompt.root; <userinput>tar -c -v -f conf/base/var.cpio.gz --format cpio --gzip var</userinput></screen>
 
-      <para>When the system boots, memory file systems for
-	<filename>/etc</filename> and <filename>/var</filename> will
+      <para>When the system boots, memory file systems
+        for <filename class="directory">/etc</filename>
+	and <filename class="directory">/var</filename> will
 	be created and mounted, and the contents of the
 	<filename>cpio.gz</filename> files will be copied into
 	them.</para>