That's not GPU passthrough. That just enables VirGL, which is a translation layer that passes some OpenGL calls through to the host's Mesa installation. It has rather poor performance though, it's extremely limited and is rather buggy too. You certainly can't use it for cutting edge gaming.
GPU passthrough is when you pass through an entire GPU device as-is to the virtual machine. That is: if you have an Nvidia RTX 3060, the guest operating system will see an Nvidia RTX 3060 and it can use the native drivers for it. This gives you near-native performance for gaming.
Now, I didn't even know this was possible with VirtualBox (if so: cool!), but it's certainly doable with KVM if you have the right motherboard and GPU combination. I have done it, but it is quite the hassle indeed though that isn't really KVM's fault.
There is a big correlation between homelessness and mental illness, personality disorder, addiction or a combination thereof. So yeah, excuse me if I don't want to deal with the paranoid schizophrenic hobo who's high on god knows what.
I can't speak for the US here, but in most civilized countries there is actually help available for homeless people and enough social systems to ensure that well adjusted people don't end up homeless in the first place. With the homeless that we do have, the difficulty usually lies in reaching them, getting them to accept the help that is available and having them durably make the necessary changes to their life to escape homelessness.
Accepting some of their anti-social behaviors is actually enabling it, and not helping them at all.
one could say RH is leaching on FOSS projects anyway
Not "one could say", that's exactly how it is.
Red Hat is standing on the shoulders of thousands of FOSS projects, and all that is asked in return is that they should allow others to stand on their shoulders too.
This doesn't even have anything to do with homeless people. Homeless people don't sleep on a window sill.
I personally know a few places in my city where people have resorted to putting spikes on their window sills like that. It has everything to do with anti-social people who think someone else's window sill is a perfectly good place to sit around all night, make noise, drink alcohol, do drugs, leave their garbage, damage the property, ...
The spikes are put there out of desperation when talking to people and talking to the police hasn't helped.
This is not anti-homeless. This is anti-idiots sitting on the window sill of the house you live in, making it a gathering place and a nuisance of themselves. A window sill is not a bench in the park.
Well the C64 didn't come with a numpad either, and the tenkeyless format is way more popular than full sized keyboards with mechanical keyboard enthusiasts, at which this keyboard is aimed.
I went numpadless 12 years ago with a Filco TKL, never looked back. A full size keyboard just feels awkward to use now with all the deskspace it takes up.
Heartbleed existed for two years before being noticed
That's a different scenario. That was an inadvertently introduced bug, not a deliberately installed backdoor. So the bad guys didn't have two years to exploit it because they didn't know about it either.
It's also not new that very old bugs get discovered. Just a few years ago a 24 year old bug was discovered in the Linux kernel.
The F-15EX, the only one for which the production line is still open, is very much a multirole fighter, developed from the Strike Eagle bomber. Sure it can do air superiority, but it can carry a shitton of weapons to strike ground targets just the same.
In the case of Arch the backdoor also wasn't inserted into liblzma at all, because at build time there was a check to see if it's being built on a deb or rpm based system, and only inserts it in those two cases.
That's committing the cardinal sin of cherrypicking your backup contents. You may end up forgetting to include things that you didn't know you needed until restore time and you're creating a backup that is cumbersome to restore. Always remember: you should really be creating a restore strategy rather than a backup strategy.
As a general rule I always backup the filesystem wholesale, optionally exclude things of which I'm 100% sure that I don't need it, and keep multiple copies (daylies and monthlies going some time back) so I always have a complete reference of what my system looked like at a particular point in time, and if push comes to shove I can always revert to a previous state by wiping the filesystem and copying one of the backups to it.
I've found that the silliest desktop problems are usually the hardest to solve, and the "serious" linux system errors are the easiest.
System doesn't boot? Look at error message, boot from a rescue disk, mount root filesystem and fix what you did wrong.
Wrong mouse cursor theme in some Plasma applications, ignoring your settings? Some weird font rendering issue? Bang your head against a wall exploring various dotfiles and rc files in your home directory for two weeks, and eventually give up and nuke your profile and reconfigure your whole desktop from scratch.
DefederateLemmyMl @ SpaceCadet @feddit.nl Posts 1Comments 584Joined 2 yr. ago