Workspace is not the same as Workstation....
Strit
joined 2 years ago
Maybe the feature is just not implemented yet?
I think maybe Enlightenment can do that, but I'm not sure.
Normally workspace definitions are systemwide not monitor specific. A workspace uses all monitors on the system.
As far as I know, only the kernel module was open sourced and in doing that Nvidia moved a lot of stuff from the driver, to the firmware/software part of their stack instead. So you would still need those, which are not open.
While the RockPro64 is great if you are looking for something ARM based, I will recommend the x64 based Odroid H3(+).
Mine has an nvme as OS drive and 2 sata SSDs as storage drives. It idles below 10W and uses like 15W under load.
Can recommend.
H3+: https://www.hardkernel.com/shop/odroid-h3-plus/
H3: https://www.hardkernel.com/shop/odroid-h3/ (what I have)
As far as I know, Windows 10 licenses are on the motherboard/BIOS, so changing the harddrive should just work.
I have heard some talk about the license getting disabled if you switch some hardware in machines as it no longer can identify it as the same machine.
This looks interesting.
So it's like PiHole, but written in Go, smaller and faster?
I agree, the UI is not really simple, but it is very functional. regarding the docker setup it also took me a couple of tries, but I succeeded in the end.
When I was a freelance contractor I used InvoiceNinja. It was pretty good and also has some apps for mobile. And it's on DockerHub too.
I second AudioBookShelf. Although I don't use it for podcasts, I use it for audiobooks, but it does do all the things you mentioned.
They did open source the kernel module:
https://github.com/NVIDIA/open-gpu-kernel-modules
But it's just a code dumb. No real history of development.
The problem, as I see it, is that the author of the original Gist does not really want wayland replacements for what he has, but rather what he has to also work on wayland.
Wayland didn't break everything. It broke what relied on X11 specific stuff, which turned out to be a lot of things. The vast majority of issues still present with Wayland are edge-cases that will only see the light of day when the people with those edge-cases start using wayland. And as long as distros default to X11, that won't happen. So that distros, like Fedora, started defaulting to Wayland "early" on (yes I put early in quotes, because it's only perceived as early) is actually a good thing. Makes the compositor developers aware of edge-cases they can't catch themselves.
I'vge been using Wayland exclusively for over a year and apart from a couple of small bugs, not even missing functions, I haven't experienced any issues relating to Wayland directly. But that's for my use case. YMMV as always.