My email provider shut down, so I had to migrate off of it. Every account I had allowed changing emails, although I had to contact customer support about some.

I tried to run some software on my router. It kind of works, if it fits. Storage was the limiting factor. There’s an option to expand the FS to include a USB stick, but somehow it made something overheat, and the router froze every now and then.

Amanita virosa. You die in horrible pain.

I love my walks (2× 30 minutes a day, usually). So does my perambulated pooch.

I’m using EFISTUB instead of a boot loader (on the PC running Arch, anyway) and Windows hasn’t figured out how to break that, yet.

Somehow it hasn’t figured out how to ruin my systemd-boot bootloader on EFI, (NixOS, this time) either. Perhaps it just has better support for EFI than BIOS?

In general, I support your stance. The devil is in the details, though, so to speak. You can only get so much evidece first-hand, and need to believe others about the rest. How do you distinguish fraudsters from honest bet mistaken people from people knowing the truth?

Fundamental logic skills also imply that atheism is a belief “God doesn’t exist!”

As an upgrade, try agnosticism: “Do we have good evidence that God exists?” So far, the only argument in favor of atheism I know of is the Occam’s Razor (those manifestations of God could also be explained in other, possibly simpler ways).

I’m running my email server on a POCO F1 ex-Android phone (running PostmarketOS now).

I wish I could get NixOS running on it, then I’d move other things also there.

I’m using VNC over an SSH tunnel. TigerVNC’s vncviewer even has the -via parameter you can use to make creating the tunnel seamless.

Here’s a couple of pointers to get started:

1. The Arch Linux Wiki is full of excellent information. It’s not for beginners, though.
2. Run top in your terminal to see what’s taking CPU.
3. Run top -o RES (or what’s easier, run top and then press M while it’s running) to see what is taking up RAM.

… though unfortunately, it’s mighty probable that the only significant consumer of memory and CPU is your browser. Get uBlock Origin, it helps web pages be lighter and eat less resources. Don’t open too many tabs at once - learn to use bookmarks efficiently, instead (folders, bookmarks toolbar and whatnot).

Reminds me of the programs that make the kernel drop FS buffers in an attempt to free up RAM. Or hog as much memory as they can in an attempt to have unused things swapped to disk. Yeah, they free up RAM all right, but at the expense of actual speed.

Most of the time, this junk is actively harmful. Forget it, modern Linux uses optimized defaults.

You can get more performance out of your hardware by switching to from heavyweight to lightweight programs - for example, instead of Skype (which uses Electron), choose some other way to chat like irssi for IRC. Instead of Gnome, choose i3 or dwm or something like that. You need a bunch of tradeoffs and learning, though, to really get the most out of your hardware.

Most of modern music sounds horrible. Elevators and shopping malls would be better off silent than blasting this noisome garbage.

There are exceptions - there totally are modern composers creating quality stuff. It’s just not played anywhere in public places, for some reason.

Not saying my practice is the best one, but here’s what I do:

• EFI system partition is mounted on /boot
  • kernel is held here. In case of distros like NixOS etc that keep around old kernels, a small ESP might run out of space. I make mine at least 1GB.
• the rest of the disk is one luks2 volume
• inside the encrypted volume, there’s a BTRFS volume
• there’s a subvolume for /home
• and a subvolume for every distro I have (which is usually 1, but sometimes I tinker or switch)
• Kernel command line parameters specify the btrfs subvol with the right distro to boot.
• for NixOS, you need a bootloader (to choose the right kernel). Systemd-boot works well, and its configuration is easily readable. I never figured out how to work with GRUB2, its configuration is just too confusing.
• or if you like Arch, dispense with bootloaders and just use EFISTUB. You can put kernel cmdline params into EFI bootloader options with efibootmgr.

Simple yet complete. Efficient, and extensible - for example, now that everything is a subvolume, I can easily snapshot it, then create backups with rsync off the snapshot, to avoid inconsistent state between backed-up files.