STEP 1. Press CTRL-H to bring up the Find/Replace Dialog.
STEP 2. Choose the “Regular expressions” checkbox near the bottom of the dialog.
STEP 3.a To add “test” to the beginning of each line, type `^` in the “Find what” field, and “test” in the “Replace with” field. Then hit “Replace All”.
STEP 3.b To add “test” to the end of each line, type `$` in the “Find what” field, and “test” in the “Replace with” field. Then hit “Replace All”.
After discovering that PHPMyAdmin is not suitable to dump or insert large databases, I did a quick search into how things are done by command line.
This worked well and my database was finally not corrupted. Host 1 is a cheap shared hosting provider with a few limitations regarding to internal data transfer, CPU and memory. Host 2 is a VPS with 4 cores, 4GB of memory with an overall decent data speed.
Be very aware of what you are doing in the next steps since it involves a drop. And when you drop the wrong database, all that’s left is the cold sweat on your forehead.
SHOW DATABASES;
DROP DATABASE [DBNAME];
CREATE DATABASE [DBNAME];
USE [DBNAME];
SOURCE [/path_to_file/DBNAME].sql;
Done.
Saucysauce and more about conditional dumping: https://www.lullabot.com/articles/importexport-large-mysql-databases
Prior to installing: 1. load the virtual drivers iso 2. set all interfaces to IDE, because old shit.
Problem:
BSOD STOP 0x0000007B on the first start of migrated virtual machine
Symptoms:
After migration of your PC into the Parallels virtual machine you receive Blue Screen of Death (BSOD) with error message STOP 0x0000007B at the first start.
Resolution:
Try to change virtual Hard Drive location to IDE
Go to the Virtual Machine Configuration -> Hardware tab -> Hard Disk 1
Change Location from SATA to IDE or from IDE to SATA.
Or use Windows installation CD to recover Windows installation. To learn how to repair your Windows Vista or Windows 7 installation in a Virtual Machine in both normal and Boot Camp Windows Virtual Machines.
[root@conrad ~]# apt-get autoremove
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up fuse (2.9.3-15+deb8u3) ...
Creating fuse device...
/run/udev or .udevdb or .udev presence implies active udev. Aborting MAKEDEV invocation.
chmod: cannot access '/dev/fuse': No such file or directory
dpkg: error processing package fuse (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
fuse
E: Sub-process /usr/bin/dpkg returned an error code (1)
I have no idea why my fuse got bonked, but I simply made a folder named fuse in the dev folder and everything works as intended again.