From: Josh Saddler <nightmorph@stork.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: hb-net-wireless.xml
Date: Tue, 20 Mar 2007 10:14:04 +0000 [thread overview]
Message-ID: <E1HTbLw-00012P-9w@stork.gentoo.org> (raw)
nightmorph 07/03/20 10:14:04
Modified: hb-net-wireless.xml
Log:
updated wpa_supplicant config file and example file locations per bug 171537. note that i went ahead and made the major version number bump slightly ahead of the actual handbook release date, so 7.0 to 8.0, as the rest of the docs will be -- because this was something that should be fixed right away, rather than wait. thanks to UberLord on IRC for confirming
Revision Changes Path
1.14 xml/htdocs/doc/en/handbook/hb-net-wireless.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-net-wireless.xml?rev=1.14&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-net-wireless.xml?rev=1.14&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-net-wireless.xml?r1=1.13&r2=1.14
Index: hb-net-wireless.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-wireless.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- hb-net-wireless.xml 28 Oct 2006 09:17:55 -0000 1.13
+++ hb-net-wireless.xml 20 Mar 2007 10:14:04 -0000 1.14
@@ -4,7 +4,7 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-wireless.xml,v 1.13 2006/10/28 09:17:55 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-wireless.xml,v 1.14 2007/03/20 10:14:04 nightmorph Exp $ -->
<sections>
@@ -12,8 +12,8 @@
Wireless isn't straight-forward. Hopefully we'll get you working!
</abstract>
-<version>7.0</version>
-<date>2006-08-30</date>
+<version>8.0</version>
+<date>2007-03-20</date>
<section>
<title>Introduction</title>
@@ -94,11 +94,12 @@
That was simple, wasn't it? However, we still have to configure
<c>wpa_supplicant</c> itself which is a bit more tricky depending on how secure
the Access Points are that you are trying to connect to. The below example is
-taken and simplified from <path>/etc/wpa_supplicant.conf.example</path> which
-ships with <c>wpa_supplicant</c>.
+taken and simplified from
+<path>/usr/share/doc/wpa_supplicant-<version>/wpa_supplicant.conf.gz</path>
+which ships with <c>wpa_supplicant</c>.
</p>
-<pre caption="an example /etc/wpa_supplicant.conf">
+<pre caption="an example /etc/wpa_supplicant/wpa_supplicant.conf">
<comment># The below line not be changed otherwise we refuse to work</comment>
ctrl_interface=/var/run/wpa_supplicant
--
gentoo-doc-cvs@gentoo.org mailing list
next reply other threads:[~2007-03-20 10:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-20 10:14 Josh Saddler [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-27 16:56 [gentoo-doc-cvs] cvs commit: hb-net-wireless.xml Marcelo Goes
2006-01-09 14:59 Jan Kundrat
2006-01-09 14:57 Jan Kundrat
2005-12-23 21:28 Xavier Neys
2005-12-21 13:16 Jan Kundrat
2005-08-02 7:41 Sven Vermeulen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1HTbLw-00012P-9w@stork.gentoo.org \
--to=nightmorph@stork.gentoo.org \
--cc=docs-team@lists.gentoo.org \
--cc=gentoo-doc-cvs@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox