You dont need to wipe anything, just shrink the filesystem from a live system.

Then create a new partition, which you encrypt and mount…

Sounds awful lot like Citrix…

They already have a forever mouse - its called Logitech MX518 - at this point its over 18 years old, and beside some small paint deficiencies it has no other issues. And it was used quite heavily - it survived years of intensive button mashing in Diablo2 and many other games…

Taking a sip of Rum and chuckles at the look on the name of my OS partition: /dev/mapper/vg-root and /dev/mapper/vg-home 🙃

There is many tutorials and how tos, this is quite nice one:

https://wiki.archlinux.org/title/LVM

BTW some filesystems like btrfs and ZFS already have a similar functionality built in…

once a month usually.

Well not really, cloning is much easier than reinstalling and then configuring everything again…

I have LVM set up from the start, so usually I just copy the /boot partition to the new disk, and the rest is in a LVM volume group, so I just use pvmove from old disk to the new one, fix the bootloader and fstab UUIDs, and Im ready to reboot from new disk, while I didnt even left my running system, no live USB needed or anything. (Of course I messed it up a first few times, so had to fix from a live OS).

But once you know all the quirks, I can be up and ready on a new drive withing 20mins (depends mainly on the pvmove), with all the stuff preserved and set

There were no real reasons to reinstall it, it works fine, occasionally had to purge some config files in home for some apps after major version changes, or edit them, but most work for years. I mean, my mplayer config is from 2009 and last edited 4 years ago…

$ head -3 /var/log/pacman.log 
[2009-04-04 12:40] installed filesystem (2009.01-1)
[2009-04-04 12:40] installed expat (2.0.1-2)
[2009-04-04 12:40] installed dbus-core (1.2.4.4permissive-1)

I installed my Arch on Desktop in 2009 and it was just cloned from one disk to another through multitude of PCs, and sure, there were occasional troubles, like upgrade from SysV init to systemd, when KDE plasma 4 released, or the time, when I had to run a custom kernel and mesa which supported the AMD Vega 56 card ~month after release.

But nowadays, I didnt had a single breakage for several years, my RX6800 GPU was well supported 3 months after release, and most things just work… BTW I run arch also on my home server, in 6 years it had literally zero issues.

Why do you use minio for image serving ? There are much better ways to do so. Nextcloud, Immich, Photoprism and others…

wasnt it a year of Linux desktop ? It after all grow by ~25% (~3% => ~4%) in a year - thats really considerable growth by every measure…

Didnt had any boot related issues since I moved to systemd-boot, even secureboot functions very well with it…

probably a 2GB 1core VPS is fine, of course more is better - faster for some stuff… Our Gitea instance run on a 4core 6GB VM…

Gitea - basically gitlab which is really easy to deploy

yes, and that command I pasted will run that /stop command inside the docker container. The same way you can list files or do any other commands on a running container:

# docker exec heimdall ls -la /
total 148
drwxr-xr-x   1 root root  4096 Jul 14 07:09 .
drwxr-xr-x   1 root root  4096 Jul 14 07:09 ..
-rwxr-xr-x   1 root root     0 Jul 14 07:09 .dockerenv
drwxr-xr-x   1 abc  abc   4096 Jul 14 07:09 app
drwxr-xr-x   1 root root  4096 Jun 17 15:30 bin
drwxr-xr-x   2 root root 12288 Jun 17 15:30 command
drwxr-xr-x   7 abc  abc   4096 Dec  3  2022 config
drwxr-xr-x   1 abc  abc   4096 Jun 23 20:35 defaults
drwxr-xr-x   5 root root   340 Aug 19 04:52 dev
-rwxr--r--   1 root root 18257 Jan  1  1970 docker-mods
drwxr-xr-x   1 root root  4096 Aug 19 04:52 etc
drwxr-xr-x   2 root root  4096 Jun 23 20:35 heimdall

just run docker exec mcbe-world /stop then just wait a bit till it shuts down cleanly and then start it again…

Hey, you can edit config files in GUI 😄