Yes, it is normal.

# fail2ban-client status sshd
Status for the jail: sshd
|- Filter
|  |- Currently failed: 10
|  |- Total failed:     4433
|  `- Journal matches:  _SYSTEMD_UNIT=ssh.service + _COMM=sshd
`- Actions
   |- Currently banned: 27
   |- Total banned:     668
   `- Banned IP list:   2.57.122.194 45.148.10.183 195.178.110.30 2.57.122.208 92.118.39.195 103.74.123.88 92.118.39.23 2.57.122.196 92.118.39.197 45.148.10.151 92.118.39.236 178.20.210.185 68.178.161.186 80.94.92.183 92.118.39.63 2.57.122.197 2.57.122.191 2.57.122.189 80.94.92.171 94.156.152.18 14.225.7.70 45.78.198.199 211.253.9.160 159.224.213.138 1.214.42.172 103.239.165.114 77.239.111.233

My choice is OpenWrt and specialized hardware. It is much better suited for home use and has much lower power consumption (i.e. silent). Right now I’m looking for replacement for my home router and going to buy one of Banana Pi boards. However in the US the optimal choice may be different.

mdam doesn’t work on either my Trixie or 26.04 install

What? Do you mean it is incompatible with Mac OS software RAID implementation? This does not mean it doesn’t work. You will also be unable to read your software RAID if you insert disks into hardware RAID device.

Much more common than is should be.

The current stable release is Debian 13. Choosing 12 is nonsense.

If you are choosing between Fedora and Debian, definitely go with Debian. Fedora evolves too rapidly for professional use, and its administration requires excessive effort.

I didn’t try many of them. I use Ansible for my job, but sometimes I hate it. I would try Terraform/OpenTofu or Salt if I were looking for alternative.

I’m hoping that’s just because I installed them on the same disk though.

No. It does not matter where they are installed.

Usually Grub successfully finds all distros installed. I guess that it fails because of some Atomic distro differences. If you use Grub from Fedora Atomic, it should also find a “normal” distro.

deleted by creator

What is it and why should we care?

you don’t really need to scale a homelab that much

Maybe. But you never know this beforehand.

if something breaks, you just want to quickly fix it manually because “doing the Ansible” is more of a pain

In most cases you just need to replay a playbook for quick fix. But I agree that the proper fix will likely take a longer time (while downtime is much shorter).

now idempotency and documentation-as-code is out of the window.

Let @BruisedMoose@piefed.social decide.

P. S. I don’t like Ansible, other tools can be easier to use. But I don’t want to recommend something concrete.

It is hard, if even possible, to keep documentation up-to-date. Better use a configuration management system (salt, ansible etc.) for your servers. Yes, you need to learn how to use it. Yes, it will take a longer time to make changes in your configuration. But as a result you’ll have a self-documented configuration-as-a-code that will allow you to scale your setup as you need. Reproducing something won’t require reading your notes, remembering your actions etc.

Absolutely wrong. Only the manual (I mean official documentation, not a “howto” in someone’s blog) can provide you a complete and up-to date information.

RTFM

It depends on what you mean by “local private network”. Probably, you need samba.

It doesn’t hide what’s under the hood and permits to fix/modify it. Yes, I’m a nerd.

I have no idea. It depends on your locale on mac.

You probably need to pass the iocharset mount option.

In matrix, chats with e2e encryption are protected from hoster even if they would try to steal your data.

I almost never use xargs. The most common case for it is find, but it is easier to use its -exec option. Also, with find your example is incorrect. You forgot that file names can contain special characters, the newline character in particular. That’s why you need to pass -print0 option to find and -0 option to xargs.