From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.43) id 1EIA4o-0002iD-2B for garchives@archives.gentoo.org; Wed, 21 Sep 2005 19:16:18 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id j8LJA5tl006420; Wed, 21 Sep 2005 19:10:05 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id j8LJA4fE009060 for ; Wed, 21 Sep 2005 19:10:04 GMT Message-Id: <200509211910.j8LJA4fE009060@robin.gentoo.org> Received: from lark.gentoo.osuosl.org ([140.211.166.177] helo=lark.gentoo.org) by smtp.gentoo.org with smtp (Exim 4.43) id 1EIA4a-0001ED-E2 for gentoo-doc-cvs@lists.gentoo.org; Wed, 21 Sep 2005 19:16:04 +0000 Received: by lark.gentoo.org (sSMTP sendmail emulation); Wed, 21 Sep 2005 19:15:49 +0000 From: "Lukasz Damentko" Date: Wed, 21 Sep 2005 19:15:49 +0000 To: gentoo-doc-cvs@lists.gentoo.org Subject: [gentoo-doc-cvs] cvs commit: mysql-upgrading.xml Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-doc-cvs@gentoo.org Reply-to: docs-team@lists.gentoo.org X-Archives-Salt: ccbbda3a-20d0-40f8-985b-03f80cabf824 X-Archives-Hash: 4454e41ba887902c3f7fbdd63dafcb7f rane 05/09/21 19:15:49 Modified: xml/htdocs/doc/en mysql-upgrading.xml Log: update from #106814 Revision Changes Path 1.2 +21 -22 xml/htdocs/doc/en/mysql-upgrading.xml 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 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 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 Index: mysql-upgrading.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/mysql-upgrading.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- mysql-upgrading.xml 11 Sep 2005 20:41:05 -0000 1.1 +++ mysql-upgrading.xml 21 Sep 2005 19:15:49 -0000 1.2 @@ -1,6 +1,6 @@ - + Upgrade guide to MySQL 4.1.x @@ -22,8 +22,8 @@ -1.0 -2005-09-11 +1.1 +2005-09-21 Upgrading from old versions of MySQL @@ -50,8 +50,8 @@

-One of the fundamental works of every database administrator is ... to make -backup of the data. So proceed with one. +One of the most important tasks that every database administrator has to perfom +is backing up data. Here we go: 

@@ -67,17 +67,18 @@
   --hex-blob \
   --master-data \
   --max_allowed_packet=16M \
+  --quote-names
   --result-file=BACKUP_MYSQL_4.0.SQL

-Now a file named BACKUP_MYSQL_4.0.SQL should exist, this one can be -used to recreate your data, the data is described in the MySQL dialect of SQL, +Now a file named BACKUP_MYSQL_4.0.SQL should exist, which later can +be used to recreate your data. The data is described in the MySQL dialect of SQL, the Structured Query Language.

-This would be a good time to see if the backup you have created is working. +Now would also be a good time to see if the backup you have created is working.

@@ -90,7 +91,7 @@

-If you have skipped step #1, you now have to create a backup package (the +If you have skipped step #1, you now have to create a backup package (of the database server, not the data) of the currently installed version:

@@ -99,7 +100,7 @@

-Now it's time to clean out the current version and all it's data: +Now it's time to clean out the current version and all of its data: 

@@ -111,10 +112,9 @@
-At this time two backup should exist, one portable between various MySQL -versions, the SQL one.
-The other instead permit to restore quickly the system at this point. Later on -this doc will be explain how to recover from this last one. +Now two different backups should exist: The SQL one, which is portable between +various versions of MySQL, and the other one that will allow you to quickly +restore your database. This will be covered later in this doc in more detail.

@@ -180,8 +180,7 @@

-If the result is not fully satisfactory, it's possible to reinstall the old -MySQL 4.0 version. +If you are not happy with MySQL 4.1, it's possible to go back to MySQL 4.0. 

@@ -189,7 +188,7 @@
 # emerge -C mysql
 # rm -rf /var/lib/mysql/ /var/log/mysql
 # emerge --usepkgonly "<mysql-4.1"
-# tar -xjpvf mysql.[tag] -C/tmp
+# tar -xjpvf mysql.[tag] -C /
 # /etc/init.d/mysql start
@@ -203,10 +202,10 @@

-Under particular conditions it's possible to upgrade directly to the next major -version of MySQL.
-If you know that this is your case, with a little trick it's possible to upgrade -straight to MySQL 4.1. +Under certain conditions it's possible to directly upgrade to the next major +version of MySQL. If you know what you're doing and think that applies to your +case, here's a little trick that makes it possible to directly upgrade to +MySQl 4.1. 

@@ -227,7 +226,7 @@

-Good luck and don't ask. +Good luck and if something fails, don't say we didn't warn you! ;-)

-- gentoo-doc-cvs@gentoo.org mailing list