My guess is that the wires/tracks could get stuck in sewage, and it might make it harder to examine the floor better due to how small the drone might be.
I had the idea of a monorail system, but I guess it would have a similar issue in case the surface the rail was attached to got faulty. Might’ve been cool looking though.
Generally during the mounting process, which is pretty early on at the OS boot process.
Yeah, that’s a risk. However you’ll always risk having leftovers from programs, even when continuing to use an OS, simply because you might switch programs, the developer rethinks where they store the config files, etc…
In most cases these files are relatively small and won’t be very noticeable in the long run. However if that still bothers you have no other choice but to cleanup your config files regardless.
Also, those config files are generally only for your own user, i.e. user-related configurations, not program-dependent ones. System configs are generally stored outside the user profiles.
Honestly, I’d argue it depends on the use case. A lightweight distro meant for basic tasks will never consume as much as a gaming one. Factoring in that your snapshots will naturally grow over time (and thus disk space) will mean that repartitioning, and getting bigger hard drives, is always a thing.
I’d still just trust the general installation guide, if it offers automatic partition allocation. Just only do partitions for /boot, / and /home, I’ve never found much use for /var /log and such as a separate partition, at least as a home user.
And when in doubt: use LVM with ext4 for dynamic partitions. BTRFS has a similar feature, but it’s still experimental, and thus potentially unstable.
I recommend making your /home a separate partition. It makes switching distros easier and also allows you to not encrypt your installation and only your own files, saving you from the headache in the case LUKS doesn’t work properly anymore.
Honestly, Sailfish is only worth it if you have a license, as there are very few native apps and the android compatibility layer is the only way to have a proper daily driver phone. I did try it with the Sony Xperia X II a 1-2 years ago, and honestly, it was still very buggy.
Generally, GrapheneOS ia pretty much the best privacy-focused android version you can have, as it will strip away anything that’s related to google while focusing on a small amount of supported devices to ensure that not many vulnerabilities are possible on the devices.
LimeageOS are less focused on privacy and more about availability. /e/OS is pretty much a downstream of LineageOS focused on Fairphones. Generally a good choice if you want android without google services.
While that is true, logging into your OS can also be done via 2FA, namely via a smartcard. It’d offer a similar protection to it, if not better.
I can also recommend Pimsleur. A bit more expensive, but features more traditional style courses, while offering a lot of what Duolingo has. Plus actual topics with grammar, not just random words!