| 1 |
swift 05/07/07 11:38:19 |
| 2 |
|
| 3 |
Modified: xml/htdocs/doc/en/draft bugzilla-howto.xml |
| 4 |
Log: |
| 5 |
Fix use of access |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.4 +12 -11 xml/htdocs/doc/en/draft/bugzilla-howto.xml |
| 9 |
|
| 10 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/bugzilla-howto.xml?rev=1.4&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 11 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/bugzilla-howto.xml?rev=1.4&content-type=text/plain&cvsroot=gentoo |
| 12 |
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/bugzilla-howto.xml.diff?r1=1.3&r2=1.4&cvsroot=gentoo |
| 13 |
|
| 14 |
Index: bugzilla-howto.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/bugzilla-howto.xml,v |
| 17 |
retrieving revision 1.3 |
| 18 |
retrieving revision 1.4 |
| 19 |
diff -u -r1.3 -r1.4 |
| 20 |
--- bugzilla-howto.xml 7 Jul 2005 11:35:16 -0000 1.3 |
| 21 |
+++ bugzilla-howto.xml 7 Jul 2005 11:38:19 -0000 1.4 |
| 22 |
@@ -1,6 +1,6 @@ |
| 23 |
<?xml version="1.0" encoding="UTF-8"?> |
| 24 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 25 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/bugzilla-howto.xml,v 1.3 2005/07/07 11:35:16 swift Exp $ --> |
| 26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/bugzilla-howto.xml,v 1.4 2005/07/07 11:38:19 swift Exp $ --> |
| 27 |
|
| 28 |
<guide link="/doc/en/bugzilla-howto.xml"> |
| 29 |
<title>Gentoo Bug Reporting Guide</title> |
| 30 |
@@ -327,14 +327,15 @@ |
| 31 |
<body> |
| 32 |
|
| 33 |
<p> |
| 34 |
-Programs often use files to get configuration information, access hardware, or |
| 35 |
-write logs. Often a program attempts to access such files incorrectly. A |
| 36 |
-program called <c>strace</c> was created to help deal with this. <c>strace</c> |
| 37 |
-traces system calls (hence the name) which mainly include accessing memory and |
| 38 |
-files. For our example, we're going to take a program foobar2. This is an |
| 39 |
-updated version of foobar. However, during the changeover to foobar2, you notice |
| 40 |
-all your configurations are missing! In foobar version 1, you had it setup to |
| 41 |
-say "foo", but now it's using the default "bar". |
| 42 |
+Programs often use files to get configuration information, get access |
| 43 |
+to hardware, or write logs. Often a program attempts to reach such files |
| 44 |
+incorrectly. A program called <c>strace</c> was created to help deal with |
| 45 |
+this. <c>strace</c> traces system calls (hence the name) which include |
| 46 |
+calls that use the memory and files. For our example, we're going to take a |
| 47 |
+program foobar2. This is an updated version of foobar. However, during the |
| 48 |
+changeover to foobar2, you notice all your configurations are missing! In |
| 49 |
+foobar version 1, you had it setup to say "foo", but now it's using the default |
| 50 |
+"bar". |
| 51 |
</p> |
| 52 |
|
| 53 |
<pre caption="Foobar2 With an invalid configuration"> |
| 54 |
@@ -535,7 +536,7 @@ |
| 55 |
|
| 56 |
<p> |
| 57 |
<uri link="http://www.bugzilla.org">Bugzilla</uri> is what we at Gentoo use to |
| 58 |
-handle bugs. Gentoo's Bugzilla is accessible by both HTTPS and HTTP. HTTPS is |
| 59 |
+handle bugs. Gentoo's Bugzilla is reachable by both HTTPS and HTTP. HTTPS is |
| 60 |
available for those on insecure networks. For the sake of consistency, I will be |
| 61 |
using the HTTPS version in the examples to follow. Head over to <uri |
| 62 |
link="https://bugs.gentoo.org">Gentoo Bugs</uri> to see how it looks. |
| 63 |
@@ -917,7 +918,7 @@ |
| 64 |
Then hit the Commit button for the changes to take place. The bug has been |
| 65 |
reassigned to me. Shortly afterward, you notice (by email usually) that I've |
| 66 |
responded to your bug. I've stated that I'd like to see an strace log to figure |
| 67 |
-out how the program is trying to access your configuration file. You follow the |
| 68 |
+out how the program is trying to reach your configuration file. You follow the |
| 69 |
previous instructions on using strace and obtain an strace log. Now you need to |
| 70 |
attach it to the bug. In order to do this, click on "Create A New Attachment". |
| 71 |
</p> |
| 72 |
|
| 73 |
|
| 74 |
|
| 75 |
-- |
| 76 |
gentoo-doc-cvs@g.o mailing list |
Archives