![]() |
Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
>On Tue, 12 Mar 2013 12:33:01 -0400 >Daniel Barrett <dbarrett at blazemonger.com> wrote: >> Alternatively install 1.18 on your new system, restore the original >> dump into it, and then upgrade it to 1.20. (If you can't upgrade the >> original wiki first.) On March 12, 2013, Rich Pieri wrote: >This will almost certainly break if you try to move between different >architectures. PowerPC to AMD64, for example. Assuming you can even get >the old database engine running on the new hardware. Hmmm... are you saying that the output of mysqldump cannot be reloaded into a database on a different architecture? That would be a significant shortcoming of mysqldump. >> Or do the transfer directly: run the scripts >> maintenance/dumpBackup.php and maintenance/importDump.php to export >> and import the XML dump of the entire wiki, respectively. > >Difficult to do if the old hardware fails and you don't have a spare. Well yes, you can't "dump from the original system" if the original system is dead. :-) Fortunately his wiki is up and running. -- Dan Barrett dbarrett at blazemonger.com
![]() |
|
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |