neysx 05/09/29 15:11:35
Modified: xml/htdocs/doc/en/draft bugzilla-howto.xml
debugging-howto.xml ldapdns-guide.xml pax-utils.xml
pocketpc-guide.xml vpnc-howto.xml
Log:
Fixed links
Revision Changes Path
1.10 +8 -8 xml/htdocs/doc/en/draft/bugzilla-howto.xml
file :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/bugzilla-howto.xml?rev=1.10&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain:
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/bugzilla-howto.xml?rev=1.10&content-type=text/plain&cvsroot=gentoo
diff :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/bugzilla-howto.xml.diff?r1=1.9&r2=1.10&cvsroot=gentoo
Index: bugzilla-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/bugzilla-howto.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- bugzilla-howto.xml 13 Jul 2005 05:48:11 -0000 1.9
+++ bugzilla-howto.xml 29 Sep 2005 15:11:35 -0000 1.10
@@ -1,8 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/bugzilla-howto.xml,v
1.9 2005/07/13 05:48:11 fox2mike Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/bugzilla-howto.xml,v
1.10 2005/09/29 15:11:35 neysx Exp $ -->
-<guide link="/doc/en/bugzilla-howto.xml">
+<guide link="/doc/en/draft/bugzilla-howto.xml">
<title>Gentoo Bug Reporting Guide</title>
<author title="Author">
@@ -108,7 +108,7 @@
<p>
This is how the Advanced Search Page looks like. While it may seem overwhelming
at first, we're going to look at a few simple areas to narrow down the rather
-vague searches bugzilla returns.
+vague searches bugzilla returns.
</p>
<figure link="/images/docs/bugzie-content.png" caption="Content"/>
@@ -229,11 +229,11 @@
<p>
Another common misconception occurs with our Documentation bugs. For example, a
user finds a bug with the <uri
-link="http://www.gentoo.org/proj/en/releng/catalyst/index.xml";>Catalyst
+link="/proj/en/releng/catalyst/index.xml">Catalyst
Docs</uri>. The general tendency is to file a bug under Docs-user, which gets
assigned to the <uri link="http://gdp.gentoo.org";>GDP</uri>, when it should
actually go to a member of the <uri
-link="http://www.gentoo.org/proj/en/releng/";>Release Engineering</uri> team. As
+link="/proj/en/releng/">Release Engineering</uri> team. As
a rule of thumb, only documentation under http://www.gentoo.org/doc/* is under
the GDP. Anything under http://www.gentoo.org/proj/* is under the respective
teams.
@@ -328,7 +328,7 @@
reference to it at any time and is preferred.
</li>
<li>
- In the Summary, you should put the package category, name, and number.
+ In the Summary, you should put the package category, name, and number.
</li>
</ul>
@@ -524,7 +524,7 @@
We'll just enter strace.log here, since that's quite self-explanatory.
</li>
<li>
- Content Type - This is the type of the file we're attaching to the bug.
+ Content Type - This is the type of the file we're attaching to the bug.
</li>
<li>
Obsoletes - If there were attachements submitted to the bug before the
current
@@ -637,7 +637,7 @@
Now shortly afterward, we find the error in the strace log and fix the bug and
mark it as RESOLVED FIXED and mention that there was a change in the location
of
configuration files, and that I will update the ebuild with a warning about it.
-The bug now becomes resolved, and you are shown the following.
+The bug now becomes resolved, and you are shown the following.
</p>
<figure link="/images/docs/bugzie-reso.png" caption="Resolved Bug"/>
1.5 +26 -26 xml/htdocs/doc/en/draft/debugging-howto.xml
file :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/debugging-howto.xml?rev=1.5&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain:
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/debugging-howto.xml?rev=1.5&content-type=text/plain&cvsroot=gentoo
diff :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/debugging-howto.xml.diff?r1=1.4&r2=1.5&cvsroot=gentoo
Index: debugging-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/debugging-howto.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- debugging-howto.xml 14 Jul 2005 09:54:37 -0000 1.4
+++ debugging-howto.xml 29 Sep 2005 15:11:35 -0000 1.5
@@ -1,8 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/draft/debugging-howto.xml,v 1.4
2005/07/14 09:54:37 fox2mike Exp $ -->
+<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/draft/debugging-howto.xml,v 1.5
2005/09/29 15:11:35 neysx Exp $ -->
-<guide link="/doc/en/debugging-howto.xml">
+<guide link="/doc/en/draft/debugging-howto.xml">
<title>Gentoo Linux Debugging Guide</title>
<author title="Author">
@@ -90,7 +90,7 @@
These errors can be quite troublesome. However, once you find them, what do
you do? The following sections will look at two important tools for handling
run time errors. After that, we'll take a look at compile errors, and how to
-handle them. Let's start out with the first tool for debugging run time
+handle them. Let's start out with the first tool for debugging run time
errors -- <c>gdb</c>.
</p>
@@ -112,7 +112,7 @@
program is to <c>emerge</c> the program with <c>FEATURES="nostrip"</c>. This
prevents the stripping of debug symbols. Why are programs stripped by default?
The reason is the same as that for having gzipped man pages -- saving space.
-Here's how the size of a program varies with and without debug symbol
stripping.
+Here's how the size of a program varies with and without debug symbol
stripping.
</p>
<pre caption="Filesize Comparison">
@@ -129,7 +129,7 @@
the size! Two more things can be done for debugging. The first is adding ggdb3
to your CFLAGS and CXXFLAGS. This flag adds more debugging information than is
generally included. We'll see what that means later on. This is how
-<path>/etc/make.conf</path> <e>might</e> look with the newly added flags.
+<path>/etc/make.conf</path> <e>might</e> look with the newly added flags.
</p>
<pre caption="make.conf settings">
@@ -138,9 +138,9 @@
</pre>
<p>
-Lastly, you can also add debug to the package's USE flags. This can be done
+Lastly, you can also add debug to the package's USE flags. This can be done
with the <path>package.use</path> file.
-</p>
+</p>
<pre caption="Using package.use to add debug USE flag">
# <i>echo "category/package debug" >> /etc/portage/package.use</i>
@@ -245,7 +245,7 @@
run_it(), and somewhere in run_it() lies the strcpy() at fault. Things such as
this help developers narrow down problems. There are a few exceptions to the
output. First off is forgetting to enable debug symbols with
-<c>FEATURES="nostrip"</c>. With debug symbols stripped, the output looks
+<c>FEATURES="nostrip"</c>. With debug symbols stripped, the output looks
something like this:
</p>
@@ -311,13 +311,13 @@
</pre>
<p>
-As you can see, -ggdb3 adds about <e>13178</e> more bytes to the file size
-over the one with debugging symbols. However, as shown above, this increase
+As you can see, -ggdb3 adds about <e>13178</e> more bytes to the file size
+over the one with debugging symbols. However, as shown above, this increase
in file size can be worth it if presenting debug information to developers.
-The backtrace can be saved to a file by copying and pasting from the
-terminal (if it's a non-x based terminal, you can use gpm. To keep this
+The backtrace can be saved to a file by copying and pasting from the
+terminal (if it's a non-x based terminal, you can use gpm. To keep this
doc simple, I recommend you read up on the documentation for gpm to see
-how to copy and paste with it). Now that we're done with <c>gdb</c>, we
+how to copy and paste with it). Now that we're done with <c>gdb</c>, we
can quit.
</p>
@@ -328,10 +328,10 @@
</pre>
<p>
-This ends the walk-through of <c>gdb</c>. Using <c>gdb</c>, we hope that you
-will be able to use it to create better bug reports. However, there are other
-types of errors that can cause a program to fail during run time. One of the
-other ways is through improper file access. We can find those using a nifty
+This ends the walk-through of <c>gdb</c>. Using <c>gdb</c>, we hope that you
+will be able to use it to create better bug reports. However, there are other
+types of errors that can cause a program to fail during run time. One of the
+other ways is through improper file access. We can find those using a nifty
little tool called <c>strace</c>.
</p>
@@ -351,8 +351,8 @@
tool called <c>strace</c> was created to help deal with this. <c>strace</c>
traces system calls (hence the name) which include calls that use the memory
and
files. For our example, we're going to take a program foobar2. This is an
-updated version of foobar. However, during the change over to foobar2, you
-notice all your configurations are missing! In foobar version 1, you had it
+updated version of foobar. However, during the change over to foobar2, you
+notice all your configurations are missing! In foobar version 1, you had it
setup to say "foo", but now it's using the default "bar".
</p>
@@ -397,7 +397,7 @@
reading in "bar" as it should. In this case, we can recommend the ebuild
maintainer to put a warning about it. For now though, we can copy over the
config file from <path>.foobar</path> and modify it to produce the correct
-results.
+results.
</p>
</body>
@@ -407,7 +407,7 @@
<body>
<p>
-<c>strace</c> is a great way at seeing what the kernel is doing to with the
+<c>strace</c> is a great way at seeing what the kernel is doing to with the
filesystem. Another program exists to help users see what the kernel is doing,
and help with kernel debugging. This program is called <c>dmesg</c>.
</p>
@@ -459,7 +459,7 @@
hdc: ATAPI 48X DVD-ROM drive, 512kB Cache, UDMA(33)
ide-floppy driver 0.99.newide
libata version 1.11 loaded.
-usbmon: debugs is not available
+usbmon: debugs is not available
</pre>
<p>
@@ -571,8 +571,8 @@
</pre>
<p>
-The program is compiling smoothly when it suddenly stops and presents an error
-message. This particular error can be split into 3 different sections, The
+The program is compiling smoothly when it suddenly stops and presents an error
+message. This particular error can be split into 3 different sections, The
compile messages, the build error, and the emerge error message as shown below.
</p>
@@ -628,7 +628,7 @@
<body>
<p>
-PORT_LOGDIR is a portage variable that sets up a log directory for separate
+PORT_LOGDIR is a portage variable that sets up a log directory for separate
emerge logs. Let's take a look and see what that entails. First, run your
emerge
with PORT_LOGDIR set to your favorite log location. Let's say we have a
location <path>/var/log/portage</path>. We'll use that for our log directory:
@@ -665,7 +665,7 @@
on as we'll see in the bug reporting section. Now that we've safely obtained
our information needed to report the bug we can continue to do so. However,
before we get started on that, we need to make sure no one else has reported
-the issue.
+the issue.
</p>
</body>
1.3 +6 -6 xml/htdocs/doc/en/draft/ldapdns-guide.xml
file :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/ldapdns-guide.xml?rev=1.3&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain:
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/ldapdns-guide.xml?rev=1.3&content-type=text/plain&cvsroot=gentoo
diff :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/ldapdns-guide.xml.diff?r1=1.2&r2=1.3&cvsroot=gentoo
Index: ldapdns-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/ldapdns-guide.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- ldapdns-guide.xml 20 Sep 2005 18:26:03 -0000 1.2
+++ ldapdns-guide.xml 29 Sep 2005 15:11:35 -0000 1.3
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/ldapdns-guide.xml,v
1.2 2005/09/20 18:26:03 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/ldapdns-guide.xml,v
1.3 2005/09/29 15:11:35 neysx Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -44,7 +44,7 @@
simply explained, a line that contains the mapping between a hostname and an IP
address). LDAP is a standard protocol to obtain information from a
hierarchically represented knowledge base (directories). The most well-known
-LDAP service for Linux is OpenLDAP, a free LDAP implementation.
+LDAP service for Linux is OpenLDAP, a free LDAP implementation.
</p>
<p>
@@ -62,7 +62,7 @@
<body>
<p>
-First, install <c>net-dns/ldapdns</c>.
+First, install <c>net-dns/ldapdns</c>.
</p>
<pre caption="Installing ldapdns">
@@ -122,7 +122,7 @@
</table>
<p>
-You should substitute the <c>127.0.0.1</c> IP address with an IP address that
+You should substitute the <c>127.0.0.1</c> IP address with an IP address that
all hosts can reach and don't forget to use the domain name you want instead of
<c>yourdomain</c>.
</p>
@@ -193,11 +193,11 @@
<p>
Bootstrap LDAP with the base dn you defined previously with
<c>ldapdns-conf</c>.
To accomplish this, we first create a file called <path>bootstrap.ldif</path>
-(it is just a name) which we fill up with DNS information.
+(it is just a name) which we fill up with DNS information.
</p>
<p>
-As an example, we provide a <uri
link="bootstrap.ldif.txt">bootstrap.ldif</uri>
+As an example, we provide a <uri link="bootstrap.ldif.txt">bootstrap.ldif</uri>
file for a fictuous domain <c>cherchetoujours.org</c>.
</p>
1.2 +2 -2 xml/htdocs/doc/en/draft/pax-utils.xml
file :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/pax-utils.xml?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain:
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/pax-utils.xml?rev=1.2&content-type=text/plain&cvsroot=gentoo
diff :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/pax-utils.xml.diff?r1=1.1&r2=1.2&cvsroot=gentoo
Index: pax-utils.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/pax-utils.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- pax-utils.xml 28 Jun 2005 11:42:43 -0000 1.1
+++ pax-utils.xml 29 Sep 2005 15:11:35 -0000 1.2
@@ -1,10 +1,10 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/pax-utils.xml,v 1.1
2005/06/28 11:42:43 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/pax-utils.xml,v 1.2
2005/09/29 15:11:35 neysx Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<guide link="/doc/en/handbook/draft/pax-utils.xml">
+<guide link="/doc/en/draft/pax-utils.xml">
<title>Gentoo PaX Utilities</title>
<author title="Author">
1.2 +41 -41 xml/htdocs/doc/en/draft/pocketpc-guide.xml
file :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/pocketpc-guide.xml?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain:
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/pocketpc-guide.xml?rev=1.2&content-type=text/plain&cvsroot=gentoo
diff :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/pocketpc-guide.xml.diff?r1=1.1&r2=1.2&cvsroot=gentoo
Index: pocketpc-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/pocketpc-guide.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- pocketpc-guide.xml 30 Aug 2005 09:04:28 -0000 1.1
+++ pocketpc-guide.xml 29 Sep 2005 15:11:35 -0000 1.2
@@ -1,8 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE guide SYSTEM "http://www.gentoo.org/dtd/guide.dtd";>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/pocketpc-guide.xml,v
1.1 2005/08/30 09:04:28 fox2mike Exp $ -->
+<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/pocketpc-guide.xml,v
1.2 2005/09/29 15:11:35 neysx Exp $ -->
-<guide link="/doc/en/pocketpc-guide.xml">
+<guide link="/doc/en/draft/pocketpc-guide.xml">
<title>Working with Pocket PCs using libsynCE</title>
<author title="Author">
@@ -37,9 +37,9 @@
</p>
<p>
-The first thing we need to do is get the kernel to recognize our device. In
+The first thing we need to do is get the kernel to recognize our device. In
this case, we have an HP iPAQ 1945. It is usb based and the module needed is
-called <c>ipaq</c>.
+called <c>ipaq</c>.
</p>
<pre caption="iPAQ Kernel Config">
@@ -66,11 +66,11 @@
<body>
<p>
-Ok, now that we have the kernel module setup, let's go ahead and get some
-information. Before we begin though, allow me to explain something. While it
-states USB Serial Converter, it's basically taking your PDA and communicating
-using serial over USB. That means this device is a USB based IPAQ. In fact,
-we even use ppp later on to create the connection. First though, let's plugin
+Ok, now that we have the kernel module setup, let's go ahead and get some
+information. Before we begin though, allow me to explain something. While it
+states USB Serial Converter, it's basically taking your PDA and communicating
+using serial over USB. That means this device is a USB based IPAQ. In fact,
+we even use ppp later on to create the connection. First though, let's plugin
our device and take a look at our modules list (note this is a udev system):
</p>
@@ -94,11 +94,11 @@
</pre>
<p>
-In the first code segment, we see that as soon as the ipaq is plugged in, the
-ipaq module is loaded (this is with coldplug of course). Not only that, but a
-quick scan of dmesg shows that our setup works, and that the device is now
-located at /dev/tts/USB0. Remember this, as we'll need it for configuration
-later on. Now that we have our device setup, let's get ahold of some packages
+In the first code segment, we see that as soon as the ipaq is plugged in, the
+ipaq module is loaded (this is with coldplug of course). Not only that, but a
+quick scan of dmesg shows that our setup works, and that the device is now
+located at /dev/tts/USB0. Remember this, as we'll need it for configuration
+later on. Now that we have our device setup, let's get ahold of some packages
that will help us communicate with it.
</p>
@@ -113,8 +113,8 @@
<body>
<p>
-Alright, the first thing we need to do is get ahold of the tools that will
-allow us to communicate with the PocketPC. So, we'll need to get ahold of the
+Alright, the first thing we need to do is get ahold of the tools that will
+allow us to communicate with the PocketPC. So, we'll need to get ahold of the
following packages:
</p>
@@ -140,7 +140,7 @@
<p>
Alright, remember that device node I told you we'd need. Here's where it comes
into play. Now, as part of the synce-serial package, we have something called
-synce-serial-config. This is what we'll use to configure the device. To do
+synce-serial-config. This is what we'll use to configure the device. To do
so, simply give it the device node from earlier:
</p>
@@ -151,8 +151,8 @@
</pre>
<p>
-Please note that when you feed synce-serial-config the device node, do it
-without the /dev. Now that we have it up and running, we can begin to use the
+Please note that when you feed synce-serial-config the device node, do it
+without the /dev. Now that we have it up and running, we can begin to use the
device.
</p>
@@ -167,9 +167,9 @@
<body>
<p>
-In order to use the IPAQ, we need to run a couple of commands. The first is
-dccm. This is our connection manager for the ipaq, and without it programs
-won't be able to connect. To use this run it <e>AS THE USER WHO WILL ACCESS
+In order to use the IPAQ, we need to run a couple of commands. The first is
+dccm. This is our connection manager for the ipaq, and without it programs
+won't be able to connect. To use this run it <e>AS THE USER WHO WILL ACCESS
SYNCE APPS</e>. So we do as so:
</p>
@@ -180,7 +180,7 @@
</pre>
<p>
-Now one more quick bit of user switching again, and we will now initiate the
+Now one more quick bit of user switching again, and we will now initiate the
connection with the device:
</p>
@@ -191,8 +191,8 @@
</pre>
<p>
-Your device should now respond to the connection. Mine does by displaying the
-sync icon and beeping to announce the connection. Now let's start by working
+Your device should now respond to the connection. Mine does by displaying the
+sync icon and beeping to announce the connection. Now let's start by working
with files.
</p>
@@ -208,15 +208,15 @@
<pre caption="IPAQ structure">
My Device
- - My Documents
- - Program Files
- - Storage Card
- - Temp
- - Windows
+ - My Documents
+ - Program Files
+ - Storage Card
+ - Temp
+ - Windows
</pre>
<p>
-Now let's see how we can copy files over. To accomplish this, we use the
tools
+Now let's see how we can copy files over. To accomplish this, we use the tools
that come with synce:
</p>
@@ -278,8 +278,8 @@
</pre>
<p>
-There we go, we have all the information about the IPAQ, which means our
-connection was successful. Now let's try to copy some files over. We use the
+There we go, we have all the information about the IPAQ, which means our
+connection was successful. Now let's try to copy some files over. We use the
pcp program for this. First, we'll copy a file "test.txt" over to the IPAQ:
</p>
@@ -289,9 +289,9 @@
</pre>
<p>
-A small note, the ':' indicates the IPAQ is the destination. Also, the IPAQ
-defaults to My Documents when you open File Explorer. However, the file is
-copied to My Device instead. If you wanted to copy it to My Documents, you
+A small note, the ':' indicates the IPAQ is the destination. Also, the IPAQ
+defaults to My Documents when you open File Explorer. However, the file is
+copied to My Device instead. If you wanted to copy it to My Documents, you
would do as such:
</p>
@@ -314,9 +314,9 @@
</pre>
<p>
-In this case, it accesses the My Documents folder, not My Device. Remember
-that when you copy over! As a final example, the IPAQ has the ability to play
-MP3's, but only with a storage card. Let's take a small folder full of mp3's
+In this case, it accesses the My Documents folder, not My Device. Remember
+that when you copy over! As a final example, the IPAQ has the ability to play
+MP3's, but only with a storage card. Let's take a small folder full of mp3's
and copy them over to the storage card (Remember, the storage card is displayed
as Storage Card in the IPAQ):
</p>
@@ -340,7 +340,7 @@
<body>
<p>
-I hope this tutorial works out for you ok. If you have any inquiries about
+I hope this tutorial works out for you ok. If you have any inquiries about
this article, please email me at <mail>[EMAIL PROTECTED]</mail>.
</p>
1.3 +54 -54 xml/htdocs/doc/en/draft/vpnc-howto.xml
file :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/vpnc-howto.xml?rev=1.3&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain:
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/vpnc-howto.xml?rev=1.3&content-type=text/plain&cvsroot=gentoo
diff :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/vpnc-howto.xml.diff?r1=1.2&r2=1.3&cvsroot=gentoo
Index: vpnc-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/vpnc-howto.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- vpnc-howto.xml 7 Aug 2005 20:15:28 -0000 1.2
+++ vpnc-howto.xml 29 Sep 2005 15:11:35 -0000 1.3
@@ -9,7 +9,7 @@
David H. Askew
</author>
-<!--
+<!--
My email address is dhaskew on earthlink.net
-->
@@ -153,7 +153,7 @@
</pre>
<p>
-If you build TUN/TAP support as a module, you first must load the <c>tun</c>
+If you build TUN/TAP support as a module, you first must load the <c>tun</c>
module:
</p>
@@ -166,7 +166,7 @@
</pre>
<p>
-Now that the <c>tun</c> module is loaded, check <c>dmesg</c> output. You
+Now that the <c>tun</c> module is loaded, check <c>dmesg</c> output. You
should see something like the following:
</p>
@@ -185,7 +185,7 @@
<body>
<p>
-Now that you have a working kernel setup, you need to install
+Now that you have a working kernel setup, you need to install
<c>net-misc/vpnc</c>:
</p>
@@ -209,7 +209,7 @@
255.255.255.0 network. The LAN in question is run by a Gentoo box using an
iptables firewall, DHCP, caching DNS, etc ... and it masquerades the LAN
behind the public IP address it receives from an ISP. You also have a
-workstation on the LAN from which you want to be able to VPN into your
+workstation on the LAN from which you want to be able to VPN into your
office with.
</p>
@@ -272,9 +272,9 @@
discuss the basics of setting up vpnc. The configuration file for vpnc
connection settings can be located in a couple places, depending on how many
profiles you want to setup. By default, vpnc looks first for
-<path>/etc/vpnc/default.conf</path> for its connection settings. If it
doesn't
+<path>/etc/vpnc/default.conf</path> for its connection settings. If it doesn't
find that file, then it looks for <path>/etc/vpnc.conf</path>. This setup will
-only address a single profile example and will use the configuration file
+only address a single profile example and will use the configuration file
location <path>/etc/vpnc.conf</path>. Make sure you do not have a
<path>/etc/vpnc/default.conf</path> file.
</p>
@@ -289,20 +289,20 @@
</pre>
<p>
-The configuration file example above should be modified to reflect the
-appropriate values for your setup. The gateway option
-<c>vpngateway.domain.org</c> can be a fully qualified domain name or an IP
-address. The ID and secret options should be given to you by a network
-administrator. If they are hesitant about giving you this info and you
-currently have a working setup on a Windows box which utilizes the official
-Cisco VPN client, then all you have to do is export your profile. The
+The configuration file example above should be modified to reflect the
+appropriate values for your setup. The gateway option
+<c>vpngateway.domain.org</c> can be a fully qualified domain name or an IP
+address. The ID and secret options should be given to you by a network
+administrator. If they are hesitant about giving you this info and you
+currently have a working setup on a Windows box which utilizes the official
+Cisco VPN client, then all you have to do is export your profile. The
user name and password options are for your normal network
sign-on, such as a Windows NT domain account.
</p>
<p>
If you are forced to export your profile from a Windows machine, then what you
-will likely have is a file ending in <path>.pcf</path>. This file will have
+will likely have is a file ending in <path>.pcf</path>. This file will have
all the information you need. Below is an example:
</p>
@@ -347,19 +347,19 @@
</pre>
<p>
-In the above example, we can see entries for <c>Host</c>, <c>GroupName</c> and
-<c>enc_GroupPwd</c>. Your <c>Username</c> and <c>UserPassword</c> may or may
+In the above example, we can see entries for <c>Host</c>, <c>GroupName</c> and
+<c>enc_GroupPwd</c>. Your <c>Username</c> and <c>UserPassword</c> may or may
not be exported depending on the setup.
</p>
<note>
-The vpnc configuration file uses an unencrypted group password (IPSec secret),
-so if you do not know the group password, but you have a copy of the encrypted
-group password from an exported profile, then you need not worry. The
encoding
-scheme for these group passwords is widely known, and all you have to do is
-visit a web page that will offer to decrypt it for you. The
+The vpnc configuration file uses an unencrypted group password (IPSec secret),
+so if you do not know the group password, but you have a copy of the encrypted
+group password from an exported profile, then you need not worry. The encoding
+scheme for these group passwords is widely known, and all you have to do is
+visit a web page that will offer to decrypt it for you. The
<uri link="http://www.unix-ag.uni-kl.de/~massar/vpnc/";>vpnc homepage</uri>
-has <uri link="http://www.unix-ag.uni-kl.de/~massar/bin/cisco-decode";>a
+has <uri link="http://www.unix-ag.uni-kl.de/~massar/bin/cisco-decode";>a
link</uri> to such a page.
</note>
@@ -376,14 +376,14 @@
<pre caption="Example vpnc-connect usage">
# <i>vpnc-connect</i>
-Enter password for [EMAIL PROTECTED]:
+Enter password for [EMAIL PROTECTED]:
VPNC started in background (pid: 14788)...
</pre>
<p>
As you can see from the above command output, once you type <c>vpnc-connect</c>
-(as root), you are prompted for your password. After entering your password,
-which will not be echoed back to you, the vpnc process will automatically
+(as root), you are prompted for your password. After entering your password,
+which will not be echoed back to you, the vpnc process will automatically
become a background process.
</p>
@@ -449,11 +449,11 @@
<p>
At this point, your workstation is capable of communicating with hosts via the
VPN, but only by IP address. As you might have noticed, vpnc did not alter
-your <path>/etc/resolv.conf</path>, thus not setting up DNS services for the
+your <path>/etc/resolv.conf</path>, thus not setting up DNS services for the
virtual link. Also, because vpnc sets your default route to your VPN gateway,
-all network traffic will travel across the VPN, even if it destined for the
-Internet or elsewhere not specifically specified by additional routes. For
-some, this basic type of connection may be satisfactory, but for most,
+all network traffic will travel across the VPN, even if it destined for the
+Internet or elsewhere not specifically specified by additional routes. For
+some, this basic type of connection may be satisfactory, but for most,
additional steps need to be taken.
</p>
@@ -465,7 +465,7 @@
<li>DNS for the VPN</li>
<li>
A routing setup that will only send traffic destined for the VPN down
- the virtual tunnel. This way, you can browse the Internet while connected
+ the virtual tunnel. This way, you can browse the Internet while connected
to the VPN, without your personal web/p2p etc ... traffic going across the
tunnel.
</li>
@@ -507,7 +507,7 @@
the traffic is destined for your VPN tunnel. This is a very functional
solution
and if you simply need to connect to the tunnel, do your work, and then
disconnect, read no further. But, if you want to be able to leave your tunnel
-connected for lengthy periods of time and don't want your work DNS servers
+connected for lengthy periods of time and don't want your work DNS servers
handling requests for your personal traffic, read on.
</p>
@@ -520,12 +520,12 @@
</p>
<note>
-We will consider VPN-related DNS queries to be any query belonging to the
+We will consider VPN-related DNS queries to be any query belonging to the
example.org domain, such as host1.example.org or server1.example.org.
</note>
<p>
-So how do you set things up, so that only requests made to hosts on the
+So how do you set things up, so that only requests made to hosts on the
example.org domain get sent to VPN supplied DNS servers? Well, you're going to
need to install a local DNS server, but don't worry, it's much easier than you
think. There are several software packages that can handle the type of setup
@@ -543,9 +543,9 @@
</pre>
<p>
-Now you need to add an option to your <c>dnsmasq</c> startup options. Edit
the
-following option to suit your needs. Substitute .example.org with the
-appropriate domain and the IP address with a valid DNS server that belongs
+Now you need to add an option to your <c>dnsmasq</c> startup options. Edit the
+following option to suit your needs. Substitute .example.org with the
+appropriate domain and the IP address with a valid DNS server that belongs
--
[email protected] mailing list
