I see posts everywhere, discussing open source products: "how shitty X is". Let me list some examples of X: systemd linux (in general, or kernel due to a lacking feature) KDE/Gnome/any other DE/WM libreoffice ubuntu or any other distro While everyone has right to complain whatever they don't like, a general attitude about open source software got my attention: Smugness. I'll create a strawman here, to not offend anyone directly, let's call him "Adam".
I'm getting old. We've been struggling with an expired root certificate at work. While the vendor was downplaying it like "naaah man you don't need to do anything, it's cool", since we have internal/external clients who are not running latest operating system with latest Google Chrome *(I'm sorry for this, I guess?), it hit us hard. While helping to solve this issue by updating certificate chains, my wife *(who is not a tech-savvy person, I guess she is also sorry for this?
I was complaining too much about inconvenience of window managers on my previous post, but I couldn't stop myself. It was a bit painful to set up everything correctly, but now I have the environment of my dreams. Heck, I can even stop using mouse, if it wasn't for those shitty electron apps. I am not sharing the configuration, since it's an environment-specific pile of hack. Just wanted to say it's still possible to code your desired configuration via AwesomeWM's powerful scripting support by investing some time.
This week was passing pretty dull, so I wanted to install some VMs to test some stuff. After realizing my disk is almost full, I've fired up partitionmanager, I saw there is some place for growth towards the end of my current partition, I decided to grow it a bit. Just as a small reenactment, some screenshots: I am using btrfs root under LUKS encrypted partition and partitionmanager was able to resize that.
Since Linux 5.2, there is a new metric in the hood: Pressure Stall Information (PSI). Currently it supplies 3 ciritical metrics from kernel: CPU, IO and memory. You can find the values simply by looking to files under /proc/pressure folder. I am not going to try explaining it in detail, since this page already does that pretty good. I've found it way better than just the load metric because of granularity.
We were using a handmade Python backup application at work. While it works, it was not practical and breaking from time to time. In that case we had to stare at the code for half an hour and ask to the single person in the company who understands its "way of doing things" eventually. So I started to look for a "better backup tool". Stumbled upon a lot of alternatives, but decided to use Restic for multiple good reasons:
I've been planning to create my own knowledgebase for a while. I believe knowledge kept secret worth nothing. Also if you're working with open source tools, it's extremely important to help others. But never found any tool convenient enough, since everything requires some weird formats to make it presentable. My notes are in Markdown format, which is pretty convenient once you set up your editor for it. I've discovered vimwiki very late, and there is an awesome helper tool for it to support Markdown -> HTML conversion.
I've been using KDE for very long time (except when it lost all of its stability in the beginning of KDE4). Lately, since everything was going smooth with my NixOS setup, I've decided to remember my good old window manager days and try out some tiling WM options. After all I am already using an extension for KWin to have tiling feature. First tried dwm since my extension tries to replicate its layouts anyway, but patching the C code for every change wasn't for me.
In Debian, package upgrades trigger restart of the related service. After I've restarted all my postgresql nodes (1 primary + 2 hot standby) at the same time, I've realized one of the secondaries were not able to process WAL files any further. Checking the logs gave me an idea: 2019-07-09 13:20:32 UTC [25065-1] postgres@[local] FATAL: the database system is starting up gzip: stdin: unexpected end of file ERROR: Remote 'barman get-wal' command has failed!
When you go to a repository, first thing you look is a README. I realized this might be the case for some of the local folders (since I am currently re-organizing). So I've defined a simple concept to keep track what's happening on a foler. The rules are simple, just create a dotfile (so it would be hidden) under any directory you feel like needs explanation: .folder-README. Afterwards add a simple check like following to your shell configuration (for me it is .