another meaningless subtitle


last update:

LineageOS in Android Oreo flavor is finally here, I guess it is time to update the guide I wrote a while back. Most of the stuff is exactly the same, for the sake of simplicity this guide will be pretty much a copy and paste of the old one with just some bits changed here and there. Required packages on Fedora are (rpmfusion repo must be previously installed): $ sudo dnf install screen java-1.

I normally move /home/user/Downloads off /home/user to a secondary mechanical drive and then symlink it back to /home/user. Firejail for security reasons does not allow whitelisting directories residing outside of the home directory, the simplest solution I found is mount Download directory using mount –bind. sudo mount --bind /mnt/data/Downloads/ /home/user/Downloads To make the change permanent edit fstab: /mnt/data/Downloads /home/user/Downloads none bind

Suunto makes some solid sport-watches, problem is that the management software is comprised of a closed source synchronization program (compatible with Windows and OSX only) and some cancerous cloud web interface accessible directly from their website. Even putting aside my personal aversion for closed source software, it is clear that this approach is retarded because an internet connection is required to be able to download any kind of data from the watch.

If I had to guess I would say that more than 90% of AMD Ryzen based builds use Single Rank memory sticks. Finding any information regarding how Dual Rank DDR4 perform, how they react to overclock or even worse, what memory settings are the best is pretty much mission impossible. Since I use Dual Rank DDR4, because, face it, it is 2017 and 16 GB of RAM does not cut it anymore, I had to dig in unexplored territories to find out what the best settings are.

LEDE, formerly OpenWRT, is a free open source Linux based operating system aimed at networking hardware. Every time the system is upgraded to a newer version using the so called “Sysupgrade BIN” image every package the user manually installed gets lost; this makes the upgrade process very tedious especially if one does not properly write down all the customization he has made. I don’t use many custom packages but QoS, USB support and vnstat are a must have.

Zabbix should theoretically be able out of the box to send alerts via XMPP. For some reason this functionality does not work as intended, luckily it is possible to specify a custom script to send alerts; combining the aforementioned script with the Perl library sendxmpp is the easiest solution to solve the issue. $ yum install sendxmpp echo “$3” | /usr/bin/sendxmpp -u <sender_user> -j <sender_domain> -p <sender_user_password> -s “$2” -i "

Zabbix is an open source resource and network monitoring system, more info: zabbix.com. The official wiki is missing some important bits regarding the installation of the tool on CentOS 7 systems. First of all, let’s add Zabbix repository and then proceed to with the installation of Zabbix and some required dependecies: $ rpm -ivh http://repo.zabbix.com/zabbix/3.4/rhel/7/x86_64/zabbix-release-3.4-1.el7.centos.noarch.rpm $ yum install mariadb mariadb-server httpd zabbix-server-mysql zabbix-web-mysql setroubleshoot .:. Configure MariaDB Login to MariaDB shell, change root’s password, create a new database for Zabbix and add a new user:

Configuring this piece of poorly documented bloated shit Mozilla came up with was a huge pain in the ass, so excuse the colored language but I am fucking pissed. The idea was to finally implement a system to synchronize Firefox’s bookmarks across multiple devices without giving Mozilla all my personal data. After some minutes spent researching the subject on the interweb I found out the synchronization system is a huge clusterfuck comprised of multiple components:

Today I had Ansible reporting an error on one of my CentOS machines while performing the usual upgrade procedure. I SSH’d into the host to check what was wrong and run “yum clean all && yum update” manually just to be greeted with the following error: rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30974) from dbenv->open: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Packages index using db3 - (-30974) error: cannot open Packages database in /var/lib/rpm CRITICAL:yum.

NFS on Fedora

NFS allows to share files and folders over network and is much much faster than samba while using way less resources. To setup a NFS server on Fedora 26 install: $ dnf install nfs-utils Shared directories are listed in the following configuration file: vi /etc/exports"> --- # Syntax # <path> <ipaddr>(<option>) /home/user/Public,sync) More information can be found here: Fedora NFS administration guide. In the above example, the the directory ‘/home/user/Public’ can be accessed by every client in the same LAN with read-only permissions.