Absitively, use case here IMO is set and forget autoupdate to stay current and SELinux (which actually reduces surface)

For a media server speed matters little (5400rpm is plenty), if you’ve only got one drive, warranty is king. Thing is you shouldn’t only have one drive, drives will fail, and warranty doesn’t get your data back, so you plan for it. At the very least, you should look at getting an offline backup as soon as possible, now you don’t care if your drive fails and can get the cheapest ones. Ideally, you also set up a RAID5 (or Unraid, or mergerfs+SnapRAID) on your server, now you just get a replacement drive and rebuild. Remember RAID is not a backup, it doesn’t protect against accidental deletions for example, so you still want the offline backup.

Also, don’t sleep on manufacturer recertified drives, as long as you have a backup they’re significantly more cost-effective.

TLDR: set yourself up so that a drive failing is not a problem.

I was here to say the same as pezhore, separating storage and compute is almost as important as separating church and state. Muck around, break things, have fun, all the while your data is safe (don’t forget offline backups though). The MS-01 is a fine looking box, but any old NUC / SFF will do for your purposes (modern AMD cpu or a graphics card if you need / want plex transcode).

Edit to add, old laptops are great compute nodes (maybe moreso from my ex corporate thinkpad laptop bias, but still)…

Or violence, which is justified self-defense when tyrants are trying to destroy everyone’s property rights.

Valid option. Burn it all down and start again is always possible, and probably more efficient than fixing things at this point.

I’m not American either, but law precedents are contagious, once enough judges think it’s reasonable, others start to as well, even across borders. A lot of the world runs on Scottish common law at base. If you really want to get to root causes, I’d go with greed, the tendency of the rich to seek rent, and Late Stage Capitalism.

The original idiocy here is the DMCA, this and the other idiocies practised in its name are consequences. Over time the idiocies build up as case law precedents until new and ever more egregious cases are made, some of which stick (as in throw shit at the wall and see what sticks) and the cycle continues. Eventually the only way to root it out becomes new legislation.

So, no-one’s mentioned tailscale. If it’s just for you, or some select friends, it’s probably the least friction to get secure access to your home network. Still, gotta check your threat matrix, do you really need it, is it really worth it for that occasional, maybe hypothetical usage ? Least access is best security…

Good to know, for such a simple thing, it’s amazing that notes hasn’t found a simple winner.

How’s that going, compared to Joplin or Standard Notes ?

My takeaway was add https://universal-blue.discourse.group/tag/announcements.rss to my rss reader (already had fedora) and I’m happy I’ll know when I need to, still for those of us who support non-technical users on these platforms it is indeed problematic.

OTOH, this is the first time I’ve had non-nvidia (sleep broken on my desktop, just rolled back and held updating for a while, no big deal) update problems in two years, which is pretty outstanding for a new rolling distro, and gives me confidence in the architecture. Shit happens I guess, but it was quickly and publicly sorted, also trust building…

You’re welcome to your opinion ;)

Fair cop on the inconveniences, although I’ve found it fine after an adaption phase, coming from fedora it was lesser than hopping to a new distro. Hard agree on knowing the nuances being problematic, clarity and accessible education is sorely missing, certainly the steepest part of the learning curve.

I just run ‘distrobox upgrade -all’ in my Daily.service, didn’t need quadlets (although after adaption I quite like them for containers now).

Why would I use a system that isn’t supposed to change if I want to change it?

There’s a bunch of benefits, atomic updates, intrinsic rollback, security of immutability, safe automatic updating and it goes on. Some things are not quite ready yet, e.g. things like sddm which should probably install themes to /etc (which they’re working on), so as often happens in linux, workarounds ensue. Making one directory mutable does not destroy all the benefits.

Yeah, I had that at the beginning, then added to my fstab

#enable sddm and therefore good themes
/var/sddm /usr/share/sddm none rbind 0 0

and KDE themes with sddm components install fine now (most themes install fine into /home, does Gnome really not have per user themes?)

Essentially you can tactically make things mutable as needed, use sparingly, but maybe not even trying lessens your opinion, no?

Yeah, I had that at the beginning, then added to my fstab

# enable sddm and therefore good themes
/var/sddm /usr/share/sddm none rbind 0 0

and then it works, kludgy, but sddm is apparently working on allowing themes in /etc, sometime soon.

Inconvenient package management

Fair.

If there’s a flatpak, no problem.

Once you realize you do package management in distroboxes rather than the main OS (rpm-ostree etc), no problem, plus you have the AUR at your disposal.

So Ima go not fair, although there is something of an education gap atm.

Be aware that halfway decent backup solutions dedupe. Which is not to say you shouldn’t clean your shit up. I vote https://github.com/qarmin/czkawka.

To a large degree, the point of RAID is to not care about drive reliability, trust the process. Also, you seem to conflate RAID with backup (“RAID is not a backup”), you want both. In a NAS, you’re probably better off with RAID5 + backup.

In a system that can take a drive failure, the current datahoarder zeitgeist is Manufacturer Recertified (Enterprise) Drives, see ServerPartDeals.com if you’re a yank, other countries have their own options.

I’d suggest you move toward a backup approach (“RAID is not a backup”) first. Assuming you have 2x10Tb, get a 3rd and copy half of your files to it, disconnect it, and now half your files are protected. Save, get another, copy the other half, now all your files are protected. If you’re trying to do RAID on USB, don’t, you are already done, otherwise (using SATA or better) you can proceed to build your array in an orderly fashion.

Narrator: They were lying about not using the data. They already had.