Gentoo Archives: gentoo-doc-cvs

From: Lukasz Damentko <rane@×××××××××××.org>
To: gentoo-doc-cvs@l.g.o
Subject: [gentoo-doc-cvs] cvs commit: mysql-upgrading.xml
Date: Wed, 21 Sep 2005 19:16:18
Message-Id: 200509211910.j8LJA4fE009060@robin.gentoo.org
1 rane 05/09/21 19:15:49
2
3 Modified: xml/htdocs/doc/en mysql-upgrading.xml
4 Log:
5 update from #106814
6
7 Revision Changes Path
8 1.2 +21 -22 xml/htdocs/doc/en/mysql-upgrading.xml
9
10 file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/mysql-upgrading.xml?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=gentoo
11 plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/mysql-upgrading.xml?rev=1.2&content-type=text/plain&cvsroot=gentoo
12 diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/mysql-upgrading.xml.diff?r1=1.1&r2=1.2&cvsroot=gentoo
13
14 Index: mysql-upgrading.xml
15 ===================================================================
16 RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/mysql-upgrading.xml,v
17 retrieving revision 1.1
18 retrieving revision 1.2
19 diff -u -r1.1 -r1.2
20 --- mysql-upgrading.xml 11 Sep 2005 20:41:05 -0000 1.1
21 +++ mysql-upgrading.xml 21 Sep 2005 19:15:49 -0000 1.2
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/mysql-upgrading.xml,v 1.1 2005/09/11 20:41:05 rane Exp $ -->
26 +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/mysql-upgrading.xml,v 1.2 2005/09/21 19:15:49 rane Exp $ -->
27
28 <guide link="/doc/en/mysql-upgrading.xml">
29 <title>Upgrade guide to MySQL 4.1.x</title>
30 @@ -22,8 +22,8 @@
31 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
32 <license/>
33
34 -<version>1.0</version>
35 -<date>2005-09-11</date>
36 +<version>1.1</version>
37 +<date>2005-09-21</date>
38
39 <chapter>
40 <title>Upgrading from old versions of MySQL</title>
41 @@ -50,8 +50,8 @@
42 <body>
43
44 <p>
45 -One of the fundamental works of every database administrator is ... to make
46 -backup of the data. So proceed with one.
47 +One of the most important tasks that every database administrator has to perfom
48 +is backing up data. Here we go:
49 </p>
50
51 <pre caption="Dump of all databases">
52 @@ -67,17 +67,18 @@
53 <i>--hex-blob \</i>
54 <i>--master-data \</i>
55 <i>--max_allowed_packet=16M \</i>
56 + <i>--quote-names</i>
57 <i>--result-file=BACKUP_MYSQL_4.0.SQL</i>
58 </pre>
59
60 <p>
61 -Now a file named <path>BACKUP_MYSQL_4.0.SQL</path> should exist, this one can be
62 -used to recreate your data, the data is described in the MySQL dialect of SQL,
63 +Now a file named <path>BACKUP_MYSQL_4.0.SQL</path> should exist, which later can
64 +be used to recreate your data. The data is described in the MySQL dialect of SQL,
65 the Structured Query Language.
66 </p>
67
68 <p>
69 -This would be a good time to see if the backup you have created is working.
70 +Now would also be a good time to see if the backup you have created is working.
71 </p>
72
73 </body>
74 @@ -90,7 +91,7 @@
75 <body>
76
77 <p>
78 -If you have skipped step #1, you now have to create a backup package (the
79 +If you have skipped step #1, you now have to create a backup package (of the
80 database server, not the data) of the currently installed version:
81 </p>
82
83 @@ -99,7 +100,7 @@
84 </pre>
85
86 <p>
87 -Now it's time to clean out the current version and all it's data:
88 +Now it's time to clean out the current version and all of its data:
89 </p>
90
91 <pre caption="Uninstall MySQL">
92 @@ -111,10 +112,9 @@
93 </pre>
94
95 <note>
96 -At this time two backup should exist, one portable between various MySQL
97 -versions, the SQL one. <br />
98 -The other instead permit to restore quickly the system at this point. Later on
99 -this doc will be explain how to recover from this last one.
100 +Now two different backups should exist: The SQL one, which is portable between
101 +various versions of MySQL, and the other one that will allow you to quickly
102 +restore your database. This will be covered later in this doc in more detail.
103 </note>
104
105 <p>
106 @@ -180,8 +180,7 @@
107 <body>
108
109 <p>
110 -If the result is not fully satisfactory, it's possible to reinstall the old
111 -MySQL 4.0 version.
112 +If you are not happy with MySQL 4.1, it's possible to go back to MySQL 4.0.
113 </p>
114
115 <pre caption="Back to the past">
116 @@ -189,7 +188,7 @@
117 # <i>emerge -C mysql</i>
118 # <i>rm -rf /var/lib/mysql/ /var/log/mysql</i>
119 # <i>emerge --usepkgonly "&lt;mysql-4.1"</i>
120 -# <i>tar -xjpvf mysql.[tag] -C/tmp</i>
121 +# <i>tar -xjpvf mysql.[tag] -C /</i>
122 # <i>/etc/init.d/mysql start</i>
123 </pre>
124
125 @@ -203,10 +202,10 @@
126 <body>
127
128 <p>
129 -Under particular conditions it's possible to upgrade directly to the next major
130 -version of MySQL.<br />
131 -If you know that this is your case, with a little trick it's possible to upgrade
132 -straight to MySQL 4.1.
133 +Under certain conditions it's possible to directly upgrade to the next major
134 +version of MySQL. If you know what you're doing and think that applies to your
135 +case, here's a little trick that makes it possible to directly upgrade to
136 +MySQl 4.1.
137 </p>
138
139 <pre caption="Straight upgrade">
140 @@ -227,7 +226,7 @@
141 </pre>
142
143 <p>
144 -Good luck and don't ask.
145 +Good luck and if something fails, don't say we didn't warn you! ;-)
146 </p>
147
148 </body>
149
150
151
152 --
153 gentoo-doc-cvs@g.o mailing list