Btrfs subvolume create /.nodelete
That way, "btrfs sub del" cannot hit your root subvolume without you first removing .nodelete .
Btrfs subvolume create /.nodelete
That way, "btrfs sub del" cannot hit your root subvolume without you first removing .nodelete .
If you set up flatpak as --user, bringing your home directory over would be 99% of the job.
It's a lot to toggle off, on each computer, multiplied by every other computer that you're connecting to. It's too insecure-by-default.
Does it support "sending a file larger than 2 gigs, without mysteriously deleting it at the end, but if you manage to sneak a hardlink to the file while it's transferring then it's okay"?
KDE connect is a large suite of some good, some half-baked, and some just plain scary remote tools.
I'm liking LocalSend for the occasional "I want some files/pictures/text to go from here to there".
And then for a hat trick, throw in Big Clive.
Lsusb, or look at the journal for the kernel enumerating the board when you plug it in.
Can the board just boot off of a usb or microsd live-image? From there, it could shove an image into its own /dev/mmcblkX.
Huh, I thought that the initial run of Copilot systems were required to use a Qualcomm processor (with advanced NPU technology).
Veritus, Arranger, The Last Moon, Mythmatch, Schim, On Your Tail, Pipistrello, Kitsune Tails.
Gzip runs at tens of MB/s. Zstd runs at least 10x faster, and then goes fasterer with multithreading (-T0).
The large /var suggests flatpak, and that plays some hardlinking games.
(If you ever need to free up / space, shifting your flatpak usage to a --user repo will help a lot. No there is no handy command for that, it's a matter of adding and deleting one package at a time.)