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

Fix a typo in the description of the wpa_supplicant.conf field

Browse source 
descriptions; it's ``private_key_passwd'' that holds the password for
the private key, not ``private_key''

While here, also fix a couple of other typos/nits.

Submitted by:	ganbold@micom.mng.net
This commit is contained in:
Giorgos Keramidas 2007-03-06 23:04:38 +00:00
parent 382ab79602
commit 36765ec4a3
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=29714
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
View file

@ -1391,7 +1391,7 @@ ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
</callout>
<callout arearefs="co-tls-pwd">
<para>The <literal>private_key</literal> field
<para>The <literal>private_key_passwd</literal> field
contains the passphrase for the private key.</para>
</callout>
</calloutlist>
@ -1518,7 +1518,7 @@ ath0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
alternative to EAP-TTLS. There are two types of PEAP
methods, the most common one is PEAPv0/EAP-MSCHAPv2. In
the rest of this document, we will use the PEAP term to
refers to that EAP method. PEAP is the most used EAP
refer to that EAP method. PEAP is the most used EAP
standard after EAP-TLS, in other words if you have a
network with mixed OSes, PEAP should be the most
supported standard after EAP-TLS.</para>
@ -2814,7 +2814,7 @@ net.link.ether.bridge_ipfw=1</programlisting>
corresponding package.</para>
<para>Once <application>ISC DHCP</application> is installed, it
needs a configuration file to run, (normally named
needs a configuration file to run (normally named
<filename>/usr/local/etc/dhcpd.conf</filename>). Here follows
a commented example, where host <hostid>margaux</hostid>
uses <application>Etherboot</application> and host