Hah, they’re TrueNAS BSD jails, but yes, now I need to figure out how to rename the “Jails” tab in my UI to overlords.
Also, all the extra work my self-hosting endeavors generate is “creep”.
Hah, they’re TrueNAS BSD jails, but yes, now I need to figure out how to rename the “Jails” tab in my UI to overlords.
Also, all the extra work my self-hosting endeavors generate is “creep”.
I use zerg units.
AFAIK everyone in the US learns about this as part of their middle school curriculum.
As i understand it, the OEM business has razor thin margins as it is. This seems like an aggressively unsustainable business practice, to the point that it’s making me wonder what their game is…
No, it doesn’t matter if the book is at a library or on my friend’s bookshelf, copyright law is literally the right to copy the thing. So if I make an illegal copy, I’m breaking copyright law. The “ToS” I’ve “agreed” to is the law of the country I’m in.
Afaik the cookie policy on your site is not GDPR compliant, at least how it is currently worded. If all cookies are “technically necessary” for function of the site, then I think all you need to do is say that. (I think for a wiki it’s acceptable to require clients to allow caching of image data, so your server doesn’t have to pay for more bandwidth).
My recommendation would be, have two machines: new hw for all your services, and use the old hw for your NAS. Each could be whatever OS you’re comfortable with using. Most everything on the services machine could be in docker configs, including network mount points to the NAS. You might be able to get away with using the 1080TI in the services box depending on what all you want to do (AI stuff, or newer stream transcoding requirements may require newer hw).
Moving the data from the old NAS to a new one without new disks will be a challenge, yes.
I have a TrueNAS box and used jails for services. I recently set up a debian box separately, and am switching from jails on truenas to docker on debian. Wish I had done this from the start.
I’d venture to guess this isn’t the first time Linus has had to deal with devs who have ideological disagreements and one quits. It’s not also his job to keep that from happening. What he said is true, there’s a process they have for maintaining Linux, and it doesn’t involve flame wars on social media…it involves flame wars over email 😅.
But seriously, if a devs are going to get upset at each other and rage quit, it’s not Linus’ job to play mediator.
Is it using wayland? I think we were able to install KDE through the software manager, but only the X version.
If you had asked me Q1 a month ago, I would have said yes (and in general, it is a yes, with enough effort). But i run endeavour (arch) and my partner runs mint (which ships with the Cinnamon WM), and a few weeks ago I recommended that she try out KDE Plasma for its wayland support. Turns out, this is not something the mint community supports, you can’t just install it through their software manager, and the mint forums will all tell you to switch to another distro that supports KDE. Meanwhile, on arch, I expect to be able to install it through pacman, choose it from SDDM, and I’m done. Maybe tweak something in my .config
, but it’s all downhill from there.
Just a datapoint. Some distros (and their communities) seem to be more receptive to experimentation than others, which can make trying new things easier/harder.
I would recommend fedora, debian, or endeavour + KDE/gnome. Good luck!
Wow, I’m impressed you actually got that working. Sounds like quite a hack.
Ooo, the MR it links to is 10mo old and still open.
Ahh, I always wondered what “pressure-vessel” was. Thanks for the resources.
Ah, I guess the HDR support in Wayland is still exposed via an “experimental” interface. But it looks like a handful of Wayland compositors support it, including wlroots which a bunch of smaller compositors are based off of.
Does it? What containerization does it use? I thought it was similar to wine, just a process pointed at a windows exe, and an environment to make the app think it’s running in a windows filesystem.
Doesn’t valve already use gamescope (Wayland compositor) with HDR support? And KDE?
Yeah, so the best beginner resource (especially for old hardware) is honestly this old blog series A Trip Through the Graphics Pipeline. But importantly, it was written before modern dx12/vulkan were around, so it will use dx9 terminogy. Also, it’s possible that certain aspects of the vulkan api aren’t possible to faithfully implement to spec with older hardware (while still maintaining reasonable performance, or possibly at all).
From there, it’s probably best to try and implement a backend for your GPU into the radv mesa driver, so probably go take a look at how other GPUs are done.
You will need to become familiar with the AMD GPU programming docs, here.
I’m not going to be one of the naysayers here who says you shouldn’t even try to do this, but as an ex-graphics driver dev, I think you will find pretty quickly that you have your work cut out for you. It would probably be easier to implement a Vulkan-on-OGL translation layer.
Both GPU hardware and drivers are developed by teams of professionals, each of which is hyper specialized in a few components, because none have the time or ability to be familiar with everything about all components (at least, not while also being effective). I’m not saying you can’t do it, and I’m not saying you wouldn’t learn a LOT doing it, but I am saying that by the time you finish, you could have worked a minimum wage job and purchased a dozen 5090s 😉.
Edit: and oh right, then there’s reading through the Vulkan spec, which, if it’s your first graphics API, will take months, if not years to digest.
We’re talking about maybe a day of my life over 20 years ago lol. I remember it being taught that it happened, but I honestly don’t remember if they emphasized how desperate for survival they were. I think it’s easy for some Americans to associate “Donner Party” with “crazy man-eating lunatic cult of the wild west” due to only retaining surface-level information on the topic.