<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Linux on Personal Blog of Maximilian Ehlers</title><link>https://blog.sodawa.com/tags/linux/</link><description>Recent content in Linux on Personal Blog of Maximilian Ehlers</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 12 Oct 2022 18:26:06 +0200</lastBuildDate><atom:link href="https://blog.sodawa.com/tags/linux/index.xml" rel="self" type="application/rss+xml"/><item><title>Extract Album Covers from Audio Tracks</title><link>https://blog.sodawa.com/blog/extract-album-covers-from-audio-files/</link><pubDate>Wed, 12 Oct 2022 18:26:06 +0200</pubDate><guid>https://blog.sodawa.com/blog/extract-album-covers-from-audio-files/</guid><description>How did I end up in this situation? My music library consists mostly of Bandcamp Albums and stuff that has been accumulated from CD Rips and friends over the years. Bandcamp Albums are tagged cleanly and usually include the covers for the Albums directly in the tracks.
I liked this way of handling the files so I added all cover.jpg directly into the audio files of the Albums I own, keeping the cover.</description></item><item><title>Postgres Update in Docker</title><link>https://blog.sodawa.com/blog/postgres-update-in-container/</link><pubDate>Wed, 13 Apr 2022 17:04:15 +0200</pubDate><guid>https://blog.sodawa.com/blog/postgres-update-in-container/</guid><description>I recently wanted to upgrade a postgres database to the latest version.
This is the workflow to achieve this with the following prerequisites:
Data of old database is inside new-data-folder Data of new database is at old-data-folder Both folders are inside the same directory Upgrading from 11 to 14 Your setup will surely differ, so just change the paths, download links and postgres version accordingly when using this.
podman pull docker.</description></item><item><title>Container Deep Diving: Part 3</title><link>https://blog.sodawa.com/blog/containers-deep-dive-part-3/</link><pubDate>Mon, 11 Apr 2022 11:42:42 +0200</pubDate><guid>https://blog.sodawa.com/blog/containers-deep-dive-part-3/</guid><description>After looking at the nitty gritty functionality of containers in Part 2 lets make life a bit easier now. First by making this post a short one and secondly by using tools for abstracting away the manual labour that had to be done in order to switch namespaces and set them up. For this lets take a look at container runtimes.
While you have probably heard of and used Docker lets talk about the common layer that underlies modern Docker and other runtimes.</description></item><item><title>Container Deep Diving: Part 2</title><link>https://blog.sodawa.com/blog/containers-deep-dive-part-2/</link><pubDate>Thu, 03 Feb 2022 11:42:42 +0200</pubDate><guid>https://blog.sodawa.com/blog/containers-deep-dive-part-2/</guid><description>Okay, so here we are in part 2 of the container post series.
At the end of part 1 we were able to identify the problems of just using chroot to achieve process isolation on a machine. With this post the goal is to have the same functionality - running bash with test-root as the new root directory with the same technologies as containers. Once that is running we will adress the problems of seeing all the network interfaces as well as still being able to kill arbitrary processes on the machine.</description></item><item><title>Container Deep Diving: Part 1</title><link>https://blog.sodawa.com/blog/containers-deep-dive-part-1/</link><pubDate>Fri, 07 Jan 2022 11:42:42 +0200</pubDate><guid>https://blog.sodawa.com/blog/containers-deep-dive-part-1/</guid><description>Containers serve 1 purpose. Selling kubernetes certificates! \s
But of course there is more to it then just hype.
Over the next few posts on my blog I would like to dig into the container world, see how we got to the current state and show what the current state actually is.
Overview So what is the real purpose of containers?
Isolate different families of processes on 1 computer from each other, so that if a process is ever compromised it does not affect any other processes on the same machine.</description></item><item><title>Fixing up QubesOS issues on a Thinkpad T460s</title><link>https://blog.sodawa.com/blog/fixing-up-qubes-issues-on-a-thinkpad/</link><pubDate>Tue, 20 Aug 2019 17:30:00 +0000</pubDate><guid>https://blog.sodawa.com/blog/fixing-up-qubes-issues-on-a-thinkpad/</guid><description>Recently I installed QubesOS for its awesome model of encapsulating different domains into VMs, all based on common template VMs, handling this with a XEN hypervisor and a Controller VM called dom0 or domain0 which includes a Desktop Environment for convenience.
This post is not an intro to the OS, the website has good documentation to read up on it.
What Id like to focus on in this post, is how I fixed a few problems that seems to be happening to some QubesOS users and Thinkpad Users in particular.</description></item><item><title>debian, docker and nftables</title><link>https://blog.sodawa.com/blog/nftables-and-docker/</link><pubDate>Wed, 24 Jul 2019 07:40:03 +0000</pubDate><guid>https://blog.sodawa.com/blog/nftables-and-docker/</guid><description>Debian Buster ships with nf_tables as the firewall backend. So when installing it on one of my machines, I wanted to use the associated nftables frontend with it as well, instead of relying on the iptables-nft compatibility layer as a default.
After all, when would be a better time for learning it than now?
On the other hand I use docker quite extensively for my development environments, and docker uses iptables to set up the correct packet forwarding rules between containers and the host.</description></item><item><title>Fixing broken Wifi after Fedora upgrade</title><link>https://blog.sodawa.com/blog/fixing-broken-wifi-after-fedora-upgrade/</link><pubDate>Sun, 15 Jul 2018 17:05:00 +0000</pubDate><guid>https://blog.sodawa.com/blog/fixing-broken-wifi-after-fedora-upgrade/</guid><description>Gnome is nagging about updates and I finally decided to run dnf upgrade.
As always it worked pretty smoothly and after a short while, my computer was up to date again.
I was able to continue my tasks and all seemed well. At least until I rebooted. Suddenly my network connections did not work anymore.
All WIFI networks are visible, but no connection wanted to work.
In this post I want to outlie the steps that I took to get it working again.</description></item><item><title>Making VSCode respect Linux key rebindings</title><link>https://blog.sodawa.com/blog/vscode-not-respecting-linux-key-rebindings/</link><pubDate>Tue, 10 Jul 2018 17:02:00 +0000</pubDate><guid>https://blog.sodawa.com/blog/vscode-not-respecting-linux-key-rebindings/</guid><description>Im using VSCode with vim-mode ALOT. So for the comfort of not having to stretch my fingers too much I have decided to switch my ESC and Capslock key.
Unfortunately though, VSCode did not seem to respect any of the changes that I had made via the gnome-tweak-tool.
AFTER WRITING IN ALL CAPS MULTIPLE TIMES I figured I should get to the bottom of this.
TL;DR
This is something that might be broken by us dispatching based on scan codes.</description></item><item><title>Connecting to IRC through bouncer</title><link>https://blog.sodawa.com/blog/connecting-to-irc-through-bouncer/</link><pubDate>Fri, 09 Mar 2018 14:18:00 +0000</pubDate><guid>https://blog.sodawa.com/blog/connecting-to-irc-through-bouncer/</guid><description>What does this do? Instead of directly connecting to an IRC server from your computer, you can have a bouncer running on your servers. This will let you stay connected to channels all the time and receive messages, which you can later read when you connect to the bouncer from home.
Another benefit is that you will appear in all chat rooms via the reverse DNS of your bouncer, and not your home IP.</description></item><item><title>Running parity on Fedora 26</title><link>https://blog.sodawa.com/blog/running-parity-on-fedora-26/</link><pubDate>Sat, 09 Sep 2017 18:54:00 +0000</pubDate><guid>https://blog.sodawa.com/blog/running-parity-on-fedora-26/</guid><description>Parity is my favourite Ethereum client. Unfortunately there are no builds ready for Fedora, which I came to appreciate recently (after switching from Arch).
The obvious solution is once again - Docker.
If you have no previous Parity data saved and you do not want to persist the files outside of your container you can pretty much just follow the instructions at https://github.com/paritytech/parity/wiki/Docker.
Otherwise you probably want to keep reading to avoid some annoyances.</description></item></channel></rss>