/me tries to understand Debian packaging / -workflow.

It's my 3rd try :D

I successfully created a Debian package for ProsodyFiler and now I'll clean things up and try to understand the details.

I should get rid of the bad habit of just writing "su" when I actually mean "su -"

Rolled out a new .zshrc + automatic tmux startup on all my hosts and containers.

Uniform look and feel in few seconds! Ansible is worth its weight in gold! 😍

Not sure why I didn't think of this earlier... but of course if makes sense to access LXD containers in their own private network via SSH using ProxyJump ... 🤦‍♂️

First I thought of making their SSH server accessible via port forwarding, then via a overlay network ... 🙄

... Today (after ~2 years of using LXD) I finally came up with the idea of just using plain old fu***** SSH ProxyJump directives.

Wow. 🤦‍♂️

... and it works like a charm!

Activated zram on one of my LXD hosts. Let's see if it helps to save some RAM ... 🤔

Fail of the day: Edited ~/.vimrc, used vi. 🤦‍♂️

Be careful with "dnf autoremove".


I'm still not sure why grub and shim were considered legacy ... 🤔

Btw: /proc/meminfo is actually in kiB (Kibibytes, pow of 2) instead kB (Kilobytes, pow of 10), although stating otherwise in its output.

There's been a discussion about it here: lore.kernel.org/patchwork/patc

.. but to not brake userspace, that mistake has persisted since then. 🤔

Gibt es hier freiwillige Tester, die gerne einmal meine neue Mailserver Anleitung für Debian Buster ansehen würden?

Sie basiert auf dem alten Setup, wurde aber in einigen Details verbessert.

Bevor ich die neue Anleitung auf die Menschheit loslasse, würde ich gerne sehen, ob sie auch wie gewünscht funktioniert ;-)

Watch out if you're running the latest version of Mastodon on a Debian Stretch Server!

The latest version of Sidekiq seems to require at least Redis 4.0.0 which is not included in Debian Stretch. You can get it from the stretch-backports repo.

$ vimtutor

After trying Emacs 1 1/2 years ago, I'm planning to dig deeper into vim. Of course I've used it, before, but more like a complete idiot than somebody who knows what he's doing. :P

it is trivial to remove kernel support for , but it is not possible to remove and keep the network stack.


Wenn ich die Motivation halten kann, werde ich mich heute Abend mal (wieder) genauer mit der Debian Paketierung beschäftigen.

Irgendwie kommt mir das alles unnötig komplex vor, und das ist dann natürlich ein Dämpfer, der schnell zu Frust führt.

Habt ihr zufällig irgendwelche wertvollen Ressourcen dazu?