{"@attributes":{"version":"2.0"},"channel":{"title":"Blogs on False Protagonist","link":"https:\/\/false.org.ru\/blog\/","description":"Recent content in Blogs on False Protagonist","generator":"Hugo","language":"en-us","copyright":"\u00a9 2022 by Rinat Sabitov","lastBuildDate":"Wed, 05 Apr 2023 07:14:07 +0000","item":[{"title":"Syncthing reappearing conflicts with the 'receive only' node","link":"https:\/\/false.org.ru\/blog\/syncthing-reappearing-conflicts-with-the-receive-only-node\/","pubDate":"Wed, 05 Apr 2023 07:14:07 +0000","guid":"https:\/\/false.org.ru\/blog\/syncthing-reappearing-conflicts-with-the-receive-only-node\/","description":"

Ok, for a long time, I’m recreating my home setup in my new place. An increasing amount of new devices led me to use syncing tools again. A syncthing<\/a> was the obvious but not easy way.<\/p>\n

I have a Raspberry Pi with a storage HDD and a desktop with my Calibre<\/a> library. The setup is simple, and it’s supposed to be easy: desktop as an introducer (Send&Recieve) and storage mounted to RPi as “Recieve Only”. It should prevent any local changes to be synced.<\/p>"},{"title":"Rotating HTTP proxies in your python script","link":"https:\/\/false.org.ru\/blog\/rotating-http-proxies-in-your-python-script\/","pubDate":"Fri, 11 Nov 2022 17:15:36 +0000","guid":"https:\/\/false.org.ru\/blog\/rotating-http-proxies-in-your-python-script\/","description":"

Ok, there can be a whole bunch of reasons why you would need to use multiple proxy servers at once. But most of them, to be honest, are related to playing around with bot detection, scrapping, and other not-so-honorable stuff.<\/p>"},{"title":"Backup and restore your SD card","link":"https:\/\/false.org.ru\/blog\/backup-and-restore-your-sd-card\/","pubDate":"Fri, 09 Sep 2022 13:29:36 +0000","guid":"https:\/\/false.org.ru\/blog\/backup-and-restore-your-sd-card\/","description":"

Backup<\/h2>\n

To get rid of empty space, we will process it via gzip<\/code><\/p>\n

$ sudo dd if<\/span>=<\/span>\/dev\/mmcblk0 conv=<\/span>sync,noerror bs=<\/span>64K | gzip -c > backup.img.gz\n<\/span><\/span><\/code><\/pre><\/div>
Restore<\/h2>\n
$ gunzip backup.img.gz\n$ sudo dd if=backup.img of=\/dev\/mmcblk0 bs=4M && sync\n<\/code><\/pre>"},{"title":"How to fix Rust tools that bind libgit2.so","link":"https:\/\/false.org.ru\/blog\/how-to-fix-rust-tools-that-bind-libgit2-so\/","pubDate":"Thu, 08 Sep 2022 11:26:51 +0000","guid":"https:\/\/false.org.ru\/blog\/how-to-fix-rust-tools-that-bind-libgit2-so\/","description":"
Recently, after a system update, I became not able to run some of the system tools written on Rust, like exa<\/code> and bat<\/code><\/p>\n
$ bat --version ~\n<\/span><\/span>bat: error while<\/span> loading shared libraries: libgit2.so.1.4: cannot open shared object file: No such file or directory\n<\/span><\/span><\/code><\/pre><\/div>
Later I’ve got<\/p>\n
.local\/share\/cargo\/bin\/cargo-install-update: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory\n<\/code><\/pre>
The fix was easy: rebuild a binary<\/p>\n
$ cargo install exa bat --force\n<\/code><\/pre>
That will rebuild a binary with new linking with current libraies<\/p>"},{"title":"How to fix yum after CentOS 8 went EOL","link":"https:\/\/false.org.ru\/blog\/how-to-fix-yum-after-centos-8-went-eol\/","pubDate":"Fri, 01 Jul 2022 07:57:56 +0000","guid":"https:\/\/false.org.ru\/blog\/how-to-fix-yum-after-centos-8-went-eol\/","description":"
\n
Error: Failed to download metadata for repo ‘appstream’: Cannot prepare internal mirrorlist: No URLs in mirrorlist<\/p>\n<\/blockquote>\n
So now we have the same issues that we had for Centos 6. And therefore we can fix it like it was described in previous post<\/a>.<\/p>\n
$ sed -i 's,baseurl=http:\/\/vault.centos.org,baseurl=http:\/\/vault.epel.cloud,g' \/etc\/yum.repos.d\/CentOS-Linux-*\n<\/code><\/pre>"},{"title":"Hardware troubleshooting","link":"https:\/\/false.org.ru\/blog\/hardware-troubleshooting\/","pubDate":"Thu, 02 Dec 2021 08:53:16 +0000","guid":"https:\/\/false.org.ru\/blog\/hardware-troubleshooting\/","description":"
Another post to the “suffering journal”. Experienced a lot of hardware fails:<\/p>\n