There’s options, simplest is Adguard DNS at the VPS. Likely better is Gluetun container + PiHole on your local network or VPS and wireguard your phone in to that (find another app), or you can just hook your phone up to free tier ProtonVPN.
Who knows, and this is why you muddy the waters as best you can with personal data and use a privacy respecting VPN, the whole Vader ‘pray I don’t alter the deal further’ thing is getting real old. Also, opt out is predatory BS (and likely quietly disregarded anyway on the basis we won’t get caught, and if we do the fines are trivial).
Easy enough to put a repo on a usb drive if that’s what you want, or indeed if you build the folder structure you can just copy. Fine for the occasional install, if you’re doing it wholesale, Ansible.
First up… backups…
You’ve got all your data on a single 8TB external drive?
This. RAID IS NOT A BACKUP !!! Sorry for shouting, but it’s that important. It’s a main storage tolerant of disk failure, you still need backups or you’re one bad ‘rm -rf’ away from losing data.
First get that second 8Tb, or better yet a 16+Tb (see serverpartdeals.com or your local equivalent for good prices on manufacturer recertified drives) so you have room to grow. Now copy that 8Tb onto it and disconnect it from your computer. Congratulations, you have a cold backup and are pretty well protected from data loss, much better than a RAID.
You can now think about a NAS with confidence, but preferably before that get another drive copy your data again and take it to a friend / relative / safety deposit box (even bury it in the back yard in something waterproof). Now you have a 3-2-1 backup strategy and you’re pretty damn well insulated against data loss.
TLDR: Backup first, NAS later.
Eh, I did 4 or 5 years on Arch, broke a lot, learned a lot, got tired of that and retired to Fedora, now Bazzite. I would recommend Arch or Cachy to someone with technical chops, which is a surprising amount of PC gamers, who wants to get up to speed fast on linux. I’ll recommend ArchWiki regardless. Then there are the others who just want to game with minimal friction, for them, Bazzite. Horses for courses… Hard agree on Ubuntu.
Duh, but it shines in immutable. Enjoy your debian, I like it too, for servers.
It’s AMD to start (7800XT), so if the screens off it uses like 6-8W anyway, then undervolt with LACT.
I think you as yet don’t quite understand the full beauty of immutable distros. Running things in distroboxes, yeah even other distros, is not a bug, it’s a feature (really) because you cannot break your main OS with a distrobox. As a developer it’s a godsend, finnicky AI project that needs a specific version of python and CUDA drivers and only has instructions for Arch ? That’s a distrobox, spin it up, play with it, archive it for later, put it away.
There’s tiers in Bazzite, for GUI apps, flatpak, if what you want isn’t there, it’s in a distrobox Arch in AUR and you can integrate it as an application into the main OS. Stuff that truly needs system level access, like zsh and intel-undervolt gets layered into the main OS with rpm-ostree. There’s security benefits as well like SELinux, but this post has gone on long enough.
It is so not an iPhone.
My second screen is a laptop (T580), also bazzite, often running moonlight to the big monitor so the main box goes to low power mode when not in use (it’s also the NAS, so no sleep, but mostly lives @ ~50W, got the GPU down to 4W idle :)
This. If you must have rooted containers docker-compose is only a
rpm-ostree install docker-compose
away, but that’s a big ass layer, you’ll feel it every update, and insecure to boot (yes I know docker finally got userspace, but how many times have you seen it used? Everywhere it’s root.). Run your docker-compose file through podlet, and there you go, userspace quadlets (95+% of the time, every time…). They’re easy to love once you get your head around them.
Agreed, when SteamOS gets more general hardware supporty things will get interesting, but Bazzite is a desktop with superlative Steam support, while SteamOS is more a steam console with desktop support. When people, especially newbs, want to do desktop things with their general purpose machines, on SteamOS they’re using Arch (bleeding edge, lower stability), while Bazzites get Fedora (sharp edge, higher stability and security) which should be a less painful and frustrating experience. Of course if there’s a flatpak (possibly the third step) it’ll be painless on either, and hey, everybody wins (except winblows) in either case.
Using wireguard to VPN into your home network is mostly trivial (using tailscale to do so is actually trivial, for my usage of the word, but introduces an untrusted company into the mix), opening your local network to the outernet is not, expect pain.
Yeah, got this one yesterday, moved to my alt on piefed for a bit…
Nah, NVLink is irrelevant for inference workloads (inference nearly all happens in the cards, models are split up over multiple and tokens are piped over pcie as necessary), mildly useful for training but you’ll get there without them.
yup, the syntax is (from within the distrobox)
distrobox-export --app appname
Run Arch in a distrobox, done (in atomic you lean hard on distrobox and flatpak).
Yup, OP has done his time in Arch meaning now competent, probably, time to go to Fedora and relax, close enough to the edge but not bleeding, good QA, For extra chill go atomic, check out uBlue…
I do it with a gluetun container (more versatile) zero issues, but you can just mainline wireguard as an interface if you prefer, also works fine, on bazzite.
Yarr !, my experience has been stellar ;) (Gaben: It’s a service problem…)
Simplest put, a fedora immutable usually keeps two images, the one you’ll boot into next reboot, and the one you’re running. If a rpm-ostree update hasn’t been run it’ll be the one you’re running and the last one. My bazzite (heavier than silverblue I guess) images are ~ 14Gb, you need room for three (the two you’re using and room for downloading the next) plus 3% of your hard drive because fedora says so, so 3*14 = 42 + .03 * 240 = 42 + 7.2 = 49.2 =~ 50Gb.
Wait a sec, when I actually do a
sudo du -sh /sysroot/ostree/deploy/fedora/deploy/*I get 14Gb for my previous one and 2.1Gb for my current one, so there’s some diff black magic fuckery (ostree chunking) going on, which makes sense because it’s not taking that long to download. So 50Gb would be super safe, you might get away with 25 depending on how different the two images are (i.e. how much has been updated), but updating to the next major fedora version (e.g. 42->43) would be iffy.
Upshot is, it shouldn’t have filled to 90-something in the first place (maybe before ostree chunking, but even then), but if you end up with a lot of entries in your GRUB they’re all taking a notable chunk of space and you’ll need to purge some.