In mt opinion systemd is a huge pain. SystemD in my eyes is a tool developed by corporation (RedHat) for other corporations (their customers). RedHat guys (and other kinds) have many things (tools, configs, manuals, trainings, webinars…) prepared for it and thus it would be pain for them to stop using it. Other corporations like it because it has support from other corporation which they can call when there is a problem and it is mostly one package which contains almost all basic stuff they will need. I see this as major selling point for it since huge corporations do not wish to play with small things, for them it is better to spend more money and buy something. In other words, it can give a lot of people work and thus a good livelihood.

Few years ago (4 or 5 I think) when I was downloading music in a hope of a higher quality the content was delivered in a 3 files, flac, cue and log. The flac file contains whole CD or album, cue is to describe where/when each song starts, ends, its name and author etc and log is a log from the program which made it. This is all nice and great if you are using some more complicated music player with library function which can create index of the songs contained in such files and play them accordingly from its UI. But as a believer that GUI is bloated I am using Music on Console player which does not have this function and is strictly reading files (so I think). So I needed to split this huge file and extract each song with correct tags.

Until “now” I was happy user of Jekyll static site generator, everything worked fine with it and blog was easy to manage. The major drawback of Jekyll (for me that is) is that it is written in Ruby and I never before worked with Ruby. Because of this I diceded to go the “easy” route and use docker image to simplify the initial installation and Jekyll management. The official docker image works fine, the only thing I needed to do was to add ruby gem local cache so it would not need to download all that mess over and over again (what a hell that is). This setup worked fine until for some reason docker started crashing from time to time. It somehow was always down after some time when I wanted to create some post. And since this is the only thing using docker on my VPS I decided to throw it away and once again jump into the rabbit hole of internet to find a good solution to replace it (I am too lazy to craft one from the ground up).

Some time ago on #artix IRC channel popped up a question on how to get the installed size of all packages in given repository and I together with other people on the channel created a one liner in shell to do exactly that. But before I have to mention that Pacman prints the “Installed size” value when we try to install packages. So one way is to try to install all packages but this can also include dependencies and may require some pacman magic which I am not aware of. I forgot to mention, this method may require root access or sudo privileges which is not good enough for me.

After a while I am writing about changes on this blog. The major changes in short are: New domain name. Self-hosted on VPS which is powered by Artix. Own git server powered by Gitea. Openring integration which provides links to articles from blogs I follow. For the future I plan some things, but the current setup is working fine so I have no idea when it will be done. The things I plan to do in the future are: