Thanks for clarifying, and I can appreciate your overall concerns as I face the same dilemma with my aging relatives.
Just to confirm, have you opened these files in Word yourself (or witnessed them being opened), to verify they are in fact valid documents? if valid, are they meant to be in English?
It wouldn't be the first time I've seen "other" files renamed with an incorrect file extension.
Assuming you meant ".docx files", those should open without issue in LibreOffice. As others have said, OnlyOffice is another popular option if format preservation is a goal.
What do you mean when you say the files are "not supported" by the tools you've tried? What, exactly, is happening and what are you trying to accomplish? The end goal wasn't clear to me from your post.
Getting Word to run under wine will require much more effort than copying the Word binary.
I think I've tried nearly every monospace typeface over the years and I've finally settled on JetBrains Mono for more than 2 years now, though IBM Plex Mono is a close second.
Looks great! I'll definitely give this a try!
You can go with something like this if you want a clean solution.
I use a drive dock station for my backup drives, and I have a few of these for one-offs too.
Crucial is fine. It's commonly found in corporate and government workstations.
I don't use RCS myself, but there are recent posts on the GOS forums and it appears to be working fine once all of the prerequisites are installed.
Sure, like I said above, GOS doesn't at all prevent you from rooting the device. They only discourage it from a security point of view. Regarding MicroG, I've never had need for it myself but I've read many other posts over the years from users who have installed it on GOS in lieu of Graphene's own implementation.
I would argue that overall GrapheneOS provides more control over the OS than some other Android-based operating systems.
They don't.
You can root GOS like any other Android-based OS. It's just highly discouraged, completely unsupported and, in the opinion of the GOS devs, you will no longer be considered to be running GOS since you are compromising the core OS by doing so.
You've clearly done your homework, and you've gotten a lot of good feedback already, so I'll just add a few points...
Storage options: Personally, I'd replace the existing drive with the highest capacity I could afford. In an ideal situation, I'd keep the host on another drive (NVMe or flash) and dedicate the large drive to a single partition of data storage.
In my own mini-PC (8th gen NUC), I've got a smaller NVMe for Proxmox and a single 8TB internal SSD for data.
Encryption: If you're going to bother with encryption, I wouldn't half-ass it. Why bother at all if you're fine using auto-decryption or a weak password that will be guessed with any sizeable effort? Just lock it down with a strong password and decrypt/mount the data drive after any reboot; making a shell alias or script for this is trivial. You're likely not rebooting the server more than once a week anyway.
Budget/Specs: I get the sense you don't have much budget right now, but knowing your hardware would help in suggesting solutions. Do you have an NVMe slot? What is the make/model of the motherboard and case?
Filesystem: For simple storage, this really doesn't matter and Ext4 will probably be fine. It's a mature, robust, no-frills filesystem which is perfect for bulk file storage (docs, music, videos, etc.), but Btrfs would be fine too if you want more options.
USB Docking Stations: I've had really good experiences with USB docking stations like this one, and I currently use it for attaching my backup HDDs each month. I wouldn't want to rely on them for realtime data access, but they do work wonderfully for backups and one-off drive access.
I've been going through my old screenshots and thought I'd share some for nostalgia. This shot is from 2007, when I was working on several logo concepts for Arch Linux (it remains one of my favourites).
As I recall, the specs were as follows:
Probably a longshot, but hoping anyone here might have working instructions on getting OpenRazer running under Fedora Silverblue. I recently picked up some Huntsman V2s and while OpenRGB works for basic control, I'd like to see what other options are available.
Apparently there is a known incompatibility between Silverblue and how OpenRazer implements kernel modules (link). I've seen elsewhere that some users have tweaked the build files to work around this, but I couldn't find any detailed info. Any help would be appreciated.
EDIT:
I got it working, but it wasn't worth the trouble compared to simply running OpenRGB in a flatpak. For Razer keyboard users, you'll gain one or two RGB presets over OpenRGB, such as Reactive, and the ability to adjust the polling rate (the merits of which are highly debatable). You'll lose secure boot and kernel verification unless you also add the ublue repo and signing key rpm (ublue-os-akmods-addons).
If anyone wants to do it anyway, I had success by downloading and installing the following ublue-os akmod rpms from here:
(Note: you might need to layer the kernel-devel package first; I had it layered already so I can't confirm.)
Add the openrazer repo, then install the daemon and frontend app:
curl -o - https://download.opensuse.org/repositories/hardware:/razer/Fedora_$(rpm -E %fedora)/hardware:razer.repo | sudo tee /etc/yum.repos.d/razer.repo
rpm-ostree install openrazer-meta razergenie
Add the plugdev group to /etc/group, then add your user to it:
sudo bash -c 'grep "plugdev" /lib/group >> /etc/group'
sudo gpasswd -a $USER plugdev
Finally, launch RazerGenie...
Not mutually exclusive, but it's highly probable that if you're running a mainstream distro, the default kernel is in lockdown mode, preventing hibernation while secure boot is enabled.