I fully flipped over every device in my house off windows about a week or two ago, and so far so good!

I’ve been daily driving linux on my personal laptop since 2009 (16 years now!?) for school / work / personal work-esque stuff, and my work laptop is now OSX. A few weeks ago I flipped my gaming machine from windows to popOS and been quite pleasantly surprised at how well gaming on Linux is these days. So much so, I convinced my wife to let me flip her gaming machine to Linux as well.

The only hiccup I’ve recently had was having to deal with windows-only, non-steam software. Ie. insta360. Luckily, there are compatibility layers / emulators I can use to be able to run it. It’s slow, but good enough.

At this point, there’s no good reason for me to go back to Windows or anything Microsoft. It’s even become a red flag when I hear a business is using Microsoft’s products. I want to hope Microsoft gets a wake up call at some point soon and turns the ship around, but I think they’ve got too many big-company deals to have to worry about their consumer products being shite.

I’d like to point out that one 747 is ~$400 mill… [source]

Linkwarden user here. Can confirm - it’s a great tool to dump links for later. I’ve setup an iOS shortcut that lets me share links directly to linkwarden. Super handy

I was thinking OP could give everyone their own VM to use as a workstation so they could access the files on the server easily, and/or run programs based on their work. When their coworkers leave, OP can easily destroy the VM and the resources would be automatically reallocated (depending on the servers configuration). With a physical device, the storage on that device is only allocated to that device and can’t be shared when it’s not in use

Me, personally? I have multiple VMs for different contexts: my teaching job (super clean, video sharing tools, presentation tools), gaming, media server (has scripts to download stuff off of YouTube), server management (just a regular Debian install), and a fuck around box (I just use it to try new OSs like Fedora, or try breaking OSs like deleting the system32 folder on windows)

I know this isn’t exactly what you’re asking for, but I’d recommend also looking into a VM OS such as proxmox or unraid (I’m running unraid)

They’ll let you create/destroy VM instances you can access remotely. So in theory, you can give everyone their own VM to use and access the files on the server.

However, unraid / proxmox may have performance issues running in a VM on a Mac mini…

This is why I’m not going to buy RAM / Dodge / Chrysler/ Jeep / anything Stellantis owns, and this is why I’m not buying any new car with “smart” / “built-in” junk.

I don’t know of any car that has an actually good head unit. Its either garbage because its a giant touch screen, making it super difficult to navigate without looking (that’s why all the controls in an airplane are different shapes and sizes), or its just a hub for you to run Android Auto / apples equivalent.

Now ads? Ffs…

They’re already making suggestions. Got one this morning telling me I can ask it for updates on Amazon packages.

Speaking of which, anyone have any suggestions for better smart speakers?

Looking through the docs n’ stuff, this is what I found:

• Updating Guide. Just basic steps, similar to what I explained above; but with commands to run.
• Backing up and restoring
• 2.0.0 Change Log. Unfortunately they don’t include any notes about how to upgrade

I wasn’t able to find any additional instructions on how to update other than the expected generic steps (docker pull or pip install -r requirements.txt). So my guess at this point is that they have scripts built in to check the version and run upgrade scripts as needed

I haven’t gone through your specific case, but generally what I do when doing a major update with potentially breaking changes:

• Read the upgrade guides, if they have them. Some devs will put them out if they know their users will encounter issues when upgrading. If they don’t have an upgrade guide, there might be some in the change logs. Going from 1.17.1 to (assuming) 2.x.y, check the change logs at 2.0.0.
• Backup everything. I’d recommend doing this on a regular basis anyway.
• (If you’re running it in a docker container) Setup a second instance, restore the backup, then run the upgrade. You’ll be able to check to see if it breaks at all. If it works, you can just destroy the old one and use the new one
• (if you’re not running it in a container) with the backup, try upgrading. If it breaks, you should be able to uninstall & reinstall the old version, then restore the backup

I haven’t gone through your specific case, but generally what I do when doing a major update with potentially breaking changes:

• Read the upgrade guides, if they have them. Some devs will put them out if they know their users will encounter issues when upgrading. If they don’t have an upgrade guide, there might be some in the change logs. Going from 1.17.1 to (assuming) 2.x.y, check the change logs at 2.0.0.
• Backup everything. I’d recommend doing this on a regular basis anyway.
• (If you’re running it in a docker container) Setup a second instance, restore the backup, then run the upgrade. You’ll be able to check to see if it breaks at all. If it works, you can just destroy the old one and use the new one
• (if you’re not running it in a container) with the backup, try upgrading. If it breaks, you should be able to uninstall & reinstall the old version, then restore the backup

I usually only keep documents and media. Programs can be redownloaded and reinstalled (and it might be better to reinstall them in case you move to a new OS anyway to ensure compatibility).

For docker specifically, only keep stuff that’s specific for your instance; which you normally setup as an external volume anyway. Docker is designed such that you should be able to nuke the container, and all persistent data is restored via an external volume on the host. If you’re not doing that, you should immediately go and set that up now (to get the data out safely, setup a volume connection such that the container path is new - that way you don’t accidentally destroy what’s there, copy the stuff you need out, then readjust the path so it’s correct)