Now that you have a working setup, make a backup. Then, experiment with either starting over and only doing a few of the steps OR experiment with removing some of those parameters. Find your minimum set of working parameters this way, then you can look them up to find out more about what each parameter does that you discovered to be essential.

I can for sure tell you that passing the render device is required for hardware transcoding, but I’m not sure what else is required. The iommu and vfio parameters are related to passing the entire gpu device into a container, but I don’t know anything about Proxmox so I can’t comment on whether that would be required for your situation.

Same here! 10gb free is more than enough for the volumes I mount on my containers with config, etc

Arch on my home server, Zorin on my laptop

I really wish the WSL extension wasn’t locked behind VS Code. My workflow is heavily reliant on it which locks me into the proprietary IDE.

Yep, you can download their “Desktop Editors”

Maybe apps will finally feel free to bundle LAME instead of forcing you to download it externally!

Yeah, I made the mistake of running Hyprland on a fresh arch install and was super confused at the lack of terminal 😅

Permanent zero-cost activation that survives reinstalls

KMS requires phoning back to MS periodically to keep the license activated. It’s still “permanent” because there’s no limit on duration (as of now at least).

HWID activation registers a hardware ID in MS servers to permanently license it. That means no renewal, just forever activation that survives reinstalls.

Just want to shout out to reviewbrah for giving us this absolute gem of a phrase

Creating a driver requires a deep understanding of some pretty low-level pieces of Linux. If you’re new to Linux, you should probably start with some “new to Linux” tutorials and get an understanding of some basic command line usage. Work your way up to being able to follow a guide on compiling the Linux kernel (without any of your own modifications). After that, you can seek out guides on creating a driver.

As a second note, fingerprint drivers are categorically difficult to work with, so this would really be jumping in on the deepest of deep ends. You can do it! But it will take a LOT of self-education.

Unfortunately, I think you’re unlikely to find anything besides the ones made by the big companies: Google, Apple, Samsung, and Garmin are the ones I know. They each have agreements with the banks and credit card companies to handle the secure exchange of data required for the touch payment system. In fact, there are still some issues resulting from a lack of cooperation (such as Citi Bank not working with Garmin Pay because they can’t be bothered to set up the relationship). I imagine an open source software would be unable to get the banks to pay attention to them to establish a partnership, or would otherwise be declined because the financial institutions wouldn’t trust them.

Depends on your distro but yes, there are Microsoft TTF fonts you can install.

https://www.zdnet.com/google-amp/article/how-to-install-microsoft-fonts-on-linux-for-better-collaboration/

That workaround has been implemented for mobile clients too https://github.com/immich-app/immich/pull/2101

Great JoCat reference 🤣

It is 100% the support. Corporations pay big money to have experts on call to fix things fast when they break, and there’s basically no other player for that kind of model in the Linux space.