Wine packages shipped by distros are now requiring ntsync, which used to be optional. If you run "modinfo ntsync" you will notice the author's name is female, and we all know foids don't do low-level and bare metal programming.At what point do we consider Linux full on trannyware?
All troons ultimately commit suicide, we have nothing to do.
I don't care. The people at CodeWeavers do excellent work.
>>109573305We're reaching levels of chud paranoid delusion previously unseen.
>>109573305Don't care Ban usury
>>109573305Linus ix just a colonel
install gentoo
>>109573305what exactly do you want troons to do? they can't work service jobs because they're unsettling and both employers and troons know this. they can't work manual labor jobs with no nuts and a festering axe wound. they can't work around children.that's why you see so many troons in the FOSS community: they sit at home all day, working on backend stuff for nonprofit distros. their only other option is death.
>>109573305Jesus fucking Christ. You are retarded. It's not some conspiracy.https://www.phoronix.com/news/Linux-6.14-NTSYNC-Driver-Readyhttps://lwn.net/Articles/974344/>At what point do we consider Linux full on trannyware?When you acknowledge that all software produced by Microsoft, Apple, Google, and Amazon is trannyware, and that Microsoft funnels over a billion dollars a year into LGBTQ++ "charities", far more than any other American corporation.
Wow, imagine my shock seeing 4troon defend troons so vigorously.>>109574821>All these well known globohomo corps deal in trannyware, so it's completely valid for my based Troonix to do it tooBefore ntsync, there were things like esync and fsync that still works well enough and they remain optional. Distros shipping Wine with a ntsync autoload requirement now forces you to move your kernel to 6.18 (first non-EOL kernel with ntsync support) or higher.
>>109573305big fucking deal, how could you possibly complain about grooves like these?https://www.youtube.com/watch?v=Eo-KmOd3i7s
>>109574696Well, what the fuck are they waiting for?
>>109575437nigga says what?backporting ntsync to < 6.18 is absolutely trivial. took me less than 10 minutes to figure out myself. there is absolutely nothing in ntsync that requires >= 6.18, that's just when the driver happened to be marked as stable and kbuild removed the dependency on BROKEN. you can apply the original kernel patch set to 6.12 straight up, only other things you need are a couple of patches from linux git that were merged after ntsync support was finished (one to fix user perms, and two that deal with timens_ktime_to_host() and friends).pic for proof.
Configure and build your own wine? Then make install. Im running 11.4 with dxvk and im on 6.12.95 and everythings fine. I totally forgot about ntsync untill ops post, its probably not neccesary.
Ah.. so the dev file /dev/ntsync was owned by root. Udev guys didnt want to change it in userspace (udevs job btw) so they made it acessible by users from kernel. Suss.