svn commit: r40959 - head/en_US.ISO8859-1/books/handbook/config

Benjamin Kaduk kaduk at MIT.EDU
Tue Feb 12 23:00:21 UTC 2013


On Tue, 12 Feb 2013, Dru Lavigne wrote:

> Modified: head/en_US.ISO8859-1/books/handbook/config/chapter.xml
> ==============================================================================
> --- head/en_US.ISO8859-1/books/handbook/config/chapter.xml	Tue Feb 12 15:09:50 2013	(r40958)
> +++ head/en_US.ISO8859-1/books/handbook/config/chapter.xml	Tue Feb 12 15:13:12 2013	(r40959)
> @@ -730,9 +711,9 @@ $sshd_enable=YES</screen>
> 	<username>root</username> console.</para>
>     </note>
>
> -    <para>To determine if a service is running, a
> -      <option>status</option> option is available.  For instance to
> -      verify that <command>sshd</command> is actually started:</para>
> +    <para>To determine if a service is running, use

I might use "whether" instead of "if"; not sure.

> +      <option>status</option>.  For instance, to verify that
> +      <command>sshd</command> is running:</para>
>
>     <screen>&prompt.root; <userinput>service sshd status</userinput>
> sshd is running as pid 433.</screen>
> @@ -1128,18 +1102,18 @@ lo0: flags=8049<UP,LOOPBACK,RUNNING,M
>
> 	<listitem>
> 	  <para>The status of the link (<literal>status</literal>) is
> -	    <literal>active</literal>, i.e., the carrier is detected.
> -	    For <devicename>dc1</devicename>, we see
> -	    <literal>status: no carrier</literal>.  This is normal
> +	    <literal>active</literal>, indicating that the carrier is

I think this would be better as "carrier signal".

> +	    detected.  For <devicename>dc1</devicename>, the
> +	    <literal>status: no carrier</literal> status is normal
> 	    when an Ethernet cable is not plugged into the
> 	    card.</para>
> 	</listitem>
> @@ -1156,44 +1130,40 @@ lo0: flags=8049<UP,LOOPBACK,RUNNING,M
>
>       <para>it would indicate the card has not been configured.</para>
>
> +      <para>To configure the card, you will need
> +	<username>root</username> privileges.  The network card
> +	configuration can be performed from the command line with
> +	&man.ifconfig.8; but will not persist after a reboot.
> +	Instead, add the network card's configuration to

Changes to rc.conf will not necessarily take effect immediately, and I 
don't know/remember exactly what conditions cause settings in rc.conf to 
be read.  Cloned wlan device configurations take effect on creation, but I 
don't know about fixed devices.  Maybe it is also on device probe/creation 
time.

In any case, the point is that this is not really an "instead" thing, more 
an "in addition" thing.  Hmm, this is sort of covered in "Testing and 
Troubleshooting", below.

> +	<filename>/etc/rc.conf</filename> using an editor.  Add a
> +	line for each network card present on the system, as seen in
> +	this example:</para>
>
> *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***

Oops.

-Ben


More information about the svn-doc-all mailing list