For flexibility and size I like external m.2 enclosures. I have some from Sabrent, Orico and Rosewill. Of them all the Rosewill is the smallest, has the nicest build quality, and seems to dissipate heat the best.
So I would recommend a Rosewill 9SIA072GJ92919, and add an NVMe SSD of your choice.
I think your MacBook is Thunderbolt 2, so you won’t get full speed but it should still be plenty fast. And this enclosure will give you TB3 speeds if you upgrade your PC later.
It’s not that one charging location was down. It’s that the current battery tech can’t charge in cold conditions without using some of its own power to heat the battery cells. This means people need to anticipate the cold and charge earlier and more often than they typically do.
Those who didn’t were stranded.
This is a real limitation of the current technology. Not a deal breaker for most people, but it’s a learning curve and a potential inconvenience.
See what’s using the space. This will list any dirs using >100MiB:
sudo du -h -d 5 -t 100M /var
Did I read right that it doesn’t use systemd?
Obligatory: Debian.
But I’d be tempted to put Proxmox on it and then run containers for each function. Then you get purpose-crafted solutions for each use case, but can easily plug new functions in or shut them down based on what you decide later.
So. Much.
Wasted
Space
Copy on write is the difference. As I understand it, a btrfs snapshot takes no space when it’s created (beyond the file system record). The filesystem is always writing changes to file chunks as a new copy of the chunk, which is then recorded as a replacement of the old chunk (which is still present on-disk). So a snapshot tracks all of these later changes, and the file system keeps the old file chunks preserved as long as you keep the snapshot. That’s why you can mount a btrfs snapshot. It just shows you the volume through the lens of all of these saved changes.
When you delete a snapshot you are then marking these preserved chunks as free space. So that is also quick.
Try Alt+Wheel