It couldn't be easier, could it? :-). In fact it is harder to undertand the documentation and the different howtos and tutorials which you can find than the process itself.

categorias:

This days i'm discovering a new Linux flavour, which it remembers me a lot to another old friend: Gentoo. It has a really similar way of installing, it's very very customizable like Gentoo, and it's quite minimalistic. I'm speaking about Archlinux.

I have to say that this days I was thinking in changing from more than 3 or 4 idilic years with Debian/Ubuntu to a more customizable system. I really don't like the last change which Ubuntu has made on the Desktop, and I really loved when I had the possibility of using last releases of software when using Gentoo (5 or 6 years ago).

So, the possibilities were mainly Gentoo... and my recent Archlinux discovery. Anyway, this is another story.

The fact is that I thought that working with Arhclinux was going to be more harder. Far from the reality. The installation is faster and not too much complicated, unlike Slackware, it has a powerfull package system with dependency resolution, and it is very customizable, so I can build it as fast as I want or as heavy and nice graphic looking as i prefer.

An example of how easy it is to do some things is shaing a folder with the vbox, (something that a fully advice against, unless you have no choice).

In the guest / Arhclinux side it was as simple as installing the module and activating:

modprobe -a vboxguest vboxsf vboxvideo

systemctl start vboxservice.service

Enjoy :-)

categorias:

Have you ever had a big (and when i say big I mean BIG) database which you need to import in a sql file?

If so, you'll probably have found this issue (or even you are having the problem just now and you are reading this looking for a solution):

ERROR 2013 (HY000): Lost connection to MySQL server

This uses to happen when trying to import the dump with the mysql -u command:

mysql -u root -p database < databasetoimport.sql

You can try to play with the my.ini settings, but a best secure solution is just to do the import from the mysql own console. How? easy.

1. go to the place where your sql is. Then log in mysql:

mysql -uroot -p

2. create the database if needed:

create database mynewdb

3. Change to it:

use mynewdb;

4. and finally, import it:

source databasetoimport.sql

Wait and hopefully the problem will not appear again.

The reason is simple. Mysql is designed to have this behabiour of closing the connection dealing with external scripts, like php or the own mysql command. If you are executing the import from inside the console, the problem will not appear.