I usually format my external drives to exFAT since it’s fully supported R/W on all major operating systems, in the slim chance I have to use macOS.

Still, no need for the OP to reformat their drive; NTFS tends to work just fine.

I need to play with HomeAssistant more. My last bit of hesitation was I was struggling to find a replacement for the announcement and intercom functionality, which is half of what my family uses Alexa for.

It looks like it got announcements with the “broadcast” intent in February; for the intercom, there may be a plugin. This seems like it might have me covered on the intercom front: https://github.com/JoeHogan/ha-intercom

Perhaps I’ll mess around with it again once the semester’s over; a lot of my family would really like to jump the Amazon ship and certainly be willing to try it if I give them the option.

I agree with other people that you should futz around with your GPU drivers and different Wayland compositors first, but also, if you ever had to reinstall, there is such thing as saving your dotfiles to significantly reduce setup time.

I don’t do that because I’m lazy, but it certainly is a thing

For reference, sharing your local IP address is a little like saying “I’m in room 223” (local IP address) and not saying what building (network) you’re in. Someone can’t walk into 223 in a different building and get to the same room you’re in.

Honestly, even if someone knew what network you were on, a local IP address wouldn’t be that useful because even if they successfully got on your network, as long as you have a properly-configured firewall and no vulnerable network-exposed services on your system, they can’t really do anything.

Honestly, while it’s still not a bright idea to tempt fate like that, even sharing your public IP isn’t that bad for the same reasons if it’s a competent home user; the worst that can happen on a properly-configured network is that someone tries and fails to exploit vulnerabilities that aren’t there and MAYBE drum up your internet bill. Also, for most ISPs, your public IP changes pretty often anyway, usually something like every few days to a week, due to changing DHCP leases.

Yes. In fact, almost every XFCE component can ran on Wayland now. At this point, they’re just a few bugs to hash out and figuring out what they’ll actually use for the compositor.

https://wiki.xfce.org/releng/wayland_roadmap

From what it sounds like, there will be a somewhat usable Wayland release in late 2026 alongside X11, and I imagine we’ll get a more polished release in late 2028.

I thought the same thing.

I haven’t used Nautilus in ages, so I can’t say for certain, but Thunar is a more traditional-feeling file manager. It feels more like an older version of the Windows file manager but with tabs, while Nautilus seems more Mac-like.

Reminds me of when a client walked in to the help desk I work at the other day with a 2015 Macbook Pro still running El Capitan. I upgraded her to Monterrey - it’s been EOL for a year, but it’s better than sending her away with El Capitan. Monterrey is the best I can do since OCLP would be outside our policy.

I mostly agree with the idea of using stable distros.

However, I will add that if you hate the default Debian installer and are willing to dig a bit through the website, they do have live USBs for each DE with a Calamares installer that I love. I really wish they would promote those more.

Honestly, they need to redo the whole Debian site.

Also, I find it funny you include 2018 in your range; I think that most things from 2018 could probably run almost any full modern distro competently, and that the better quality devices from 2015-2017 also wouldn’t struggle too much.

Debian with XFCE. It’s very stable with very little bloat compared to Ubuntu.

KDE might not run horribly, but XFCE was always snappy for me when I ran it on a similarly-aged, sinmilar performance Fujitsu Lifebook.

I’ve never even owned a Mac; I know about it because I’ve Hackintoshed a few times, so I’m familiar with OpenCore.

Really? I thought the last version for those was Monterrey and that that went EOL in 2024.

That reminds me; the other day a client walked up to the help desk I work at with a 2015 MBP still running El Capitan.

I’m confused. How did you save your parent’s Masters in Business Administration? /s

(Sorry. I can’t help but think that every time someone acronym’s Macbook Air.)

OCLP?

I will point out that the card support for ROCm has improved; AMD explicitly supports most RDNA3 or later consumer GPUs, and I think support might go back to RDNA2, maybe RDNA1.

Supposedly it’s technically possible to use Polaris, but it’s very broken at this point.

The Arch Wiki is probably the sungle most useful documentation for any Linux user; I don’t even use Arch and it’s still extremely helpful.

I could see the benefits of using Arch just so almost every function my system has is near-perfectly documented in Arch Wiki.

As for the distro itself, it has the newest packages, and often good repos with interesting packages that Debian and others may lack. It also expects you to choose and install the components you want, whereas the Debian installer will usually just install defaults; you can use Debootstrap for a minimal Debian install, but that’s not as well supported for installing Debian due to the way tools as set up on the install medium.

The reason I choose Debian over Arch is because if I don’t use a device for several months and have to install updates (like my school laptop over the summer), Debian Stable is more likely to survive that than Arch; I’ve destroyed several Arch VMs by trying to update them after not using them for months. I’m sure I could have salvaged them if I tried, but I’d rather just make a new VM.

That’s precisely why secure boot and TPMs exist - the TPM can store the keys to decrypt the drives and won’t give them unless the signed shim executable can be verified; the shim executable then checks the kernel images, options, and DKMS drivers’ signatures as well. If the boot partition has been tampered with, the drive won’t decrypt except by manual override.

The big problem is Microsoft controls the main secure boot certificate authority, rather than a standards body. This means that either a bad actor stealing the key or Microsoft itself could use a signed malicious binary used to exploit systems.

Still, it’s at least useful against petty theft.

TPM sniffing attacks seem possible, but it looks like the kernel uses parameter and session encryption by default to mitigate that: https://docs.kernel.org/security/tpm/tpm-security.html

It looks like NetBSD and OpenBSD might be good OSs for 32-bit; the next FreeBSD version is dropping support. I don’t use any BSDs, but I think a BSD is probably the best-supported modern Unix operating system for this kind of hardware as the last of the major distros drop i386.

Linux distro support is really thinning out for x86_32, so for this use case; I’m sure the distros still exist, but they’re often niche projects. Gentoo may do the trick if you want to; I can’t tell if they compile their newfangled precompiled packages for i386 though, so if they don’t, you’ll probably have to set up a cross compiling setup from a more powerful x86_64 machine, which you’d need to use every time you update.

That joke’s so funny, it’s making me a bit wheezy…

Didn’t Debian drop i386? Are you running Debian Bookworm?