Innodb: pros and cons

If you have to sync different devices you could have many problems with Innodb engine.

But on the other hand, it has some advantages: is more modern than MyIsam, and support foreign keys.

A compromise can be have Innodb as engine, but all the tables in MyIsam.
You should in any way be careful with some files, as already explained, in particular ibdata1.

how get rid of Innodb

If you don’t need foreign kayes, you can get rid of Innodb in /etc/my.cnf, with these instructions (stop mariadb before, and restart after):

default-storage-engine=MyISAM


Linux fstab to mount different fs with the same label

If you have different partitions (such as USB ones) with the same label (so that you can syncro them with the same script) but with different filesystem (such as btrfs and ext4) you can modify your fstab line using auto instead of etx4 or btrfs.

I mean something like this:

LABEL="your-label"  /media/your-mount-path  auto  users,noauto,noatime,nodiratime  0  2

In this way you will be able to mount your usb devices (either etx4 or btrfs or another fs) without problems.

Syncthing’s problems

If you are not able to connect your PC to your mobile device, using Syncthing in both of them, you should check your firewall, both on PC and on mobile.
And, of course you have to set, in firewalls, permissions to communicate each other.

syncing firefox

Symlinking logins.json is not possibile, you have to copy it every time. And it is necessary that logins.json matchs to key4.db.

Krusader: per sincronizzare

all’inizio

si può aprire da terminale Krusader scegliendo quale pannello debba stare a sinistra e quale a destra, ad esempio
“krusader –left /path –right /media/path”

escludere certi (tipi di) files dalla sincrinizzazione

In file filter anteporre | al tipo di file. Ad esempio “| *.ini” per escludere dalla sincro i files con estensione ini.