foxbox – Page 11 – Fox’s Projects

Doing a large MySQL dump

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.

Keep the passwords ready for both hosts.

HOST 1

mysqldump -u [USERNAME] -p [DBNAME] | gzip > [/path_to_file/DBNAME].sql.gz

Copy the file over to Host 2

HOST 2

gzip -d [/path_to_file/DBNAME].sql.gz

[/path_to_mysql/]mysql -u [USERNAME] -p

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

BSOD STOP 0x0000007B

TLDR;

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
1. Go to the Virtual Machine Configuration -> Hardware tab -> Hard Disk 1
2. 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.

Quick request for directory size

Directory Size:

du -csh

Note: du -h works too, but fills your screen up with text when you only want to know the size of that directory.

Compressing data

Compressing Directory:

tar -zcvf archive-name.tar.gz directory-name

Add date:

tar -zcvf filename_$(date +%y%m%d).tar.gz directory-name

Decompressing File:

tar -zxvf archive-name.tar.gz

Note: I always do -v as I would like to see what’s happening and it looks cool. \@_@/

Users and Passwords in Linux

Add user: adduser [username]
Change password: passwd [username]

Adding SSH keys to Github

For Debian 9 (and MacOS)

Check for old keys
1. ```
cd ~/.ssh
```
2. ```
ls id_*
```
Backup old keys
1. ```
mkdir keys_backup
```
2. ```
cp id_* keys_backup
```

Generate a new key

ssh-keygen -t rsa -C "your_email@example.com"

don’t use a passphrase

Go to the key directory
1. ```
cd ~/.ssh
```
Download the public key
Open the key in Notepad++ (or similar)
Log in at github.com
Click on the right side on your profile picture
Click on Settings
Click on SSH and GPG Keys
Click on New SSH Key
Create a new name for the key
Paste the contents of the public key into the Key field
Click on Add SSH Key

Done.

I fixed my fuse in Debian 8

[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.

In-place upgrade of a Themelr template (Joomla)

How to Fix the error after updating to Joomla 3.9

If you updated to the latest version and the following error appears when you try to launch Themler please follow the instruction below:

Fatal error: require_once(): Failed opening required '[...]/administrator/includes/toolbar.php' (include_path='.:/usr/lib/php7.2') in [...]/templates/[theme_name]/app/index.php on line 25

Open theme folder on the server: www/Joomla_directory/templates;
open /app folder;
open index.php for editing in any html or text editor;
find the line
require_once JPATH_BASE . DS . 'includes' . DS . 'toolbar.php';
and replace it with the following line:
$prefix = version_compare(JVERSION, '3.9', '>=') ? 'sub' : ''; require_once JPATH_BASE . DS . 'includes' . DS . $prefix . 'toolbar.php';;
open /app/start folder;
open data.php file for editing and follow step 4;
open manifest.php file for editing and follow step 4;
start Themler.

Final update about the JBL Speaker

It’s well established that it is a fake. It’s well constructed as everything sits pretty well together with only 8 screws. From that I’ve seen, the original speaker has many many more screws.

So, the logic board is quite different from the original and it has 2 speakers instead of four. I recommend you look at this video to see how the original inside looks like: LINK

Now look on how the Chinese JBL looks on the inside:

If you want to upgrade it, have a look here: LINK

Fake JBL Xtreme update

I am trying to connect the official app to it and it cannot detect the speaker. Assuming that the software is written correctly, I think that the inside of this speaker differs from the original. Oh well!