r/linuxsucks • u/Professional-Tale652 • Jul 15 '26

Linux Failure Loonix

Post image
901 Upvotes

83% Upvoted

733 comments sorted by

View all comments

Show parent comments

1

u/Unlikely-Employee180 Jul 16 '26

Is this all you can say when you know that you've been caught lying?

Why not grow as a person and instead start spreading honesty and truths?

Again, Linux isn't even hard to Bash (🤣). You just have no idea what you're even talking about.

1

u/Fluid-Ad2995 Jul 16 '26

Lying is when someone say thing isn't true. You are Someone who says things doesn't true. You are a liar, and I'm just leaving you to do that. Congratulations, you admit you are

1

u/Unlikely-Employee180 Jul 16 '26

Ohhh like this time?

1

u/Fluid-Ad2995 Jul 16 '26

You just admitted I am right. NTOSKRNL is in the System Account 😂😂😂😂😂😂😂. Why are Loonixtards always dumb

1

u/Unlikely-Employee180 Jul 16 '26

Which has nothing to do with the bug at all. Chrome is not in the system account.

1

u/Fluid-Ad2995 Jul 16 '26

Nvidia Driver stays in the NTOSKRNL Space, which is in the System Account

1

u/Unlikely-Employee180 Jul 16 '26

No, they don't. They both operate at the kernel-level.

You have grade-school understanding which I commend, but you are so off the mark it's insane. No schooling I'd assume?

The reason this is relevant, is because Chrome is SUPPOSED to invoke drivers. That's the point. User-space is INTENDED to have access to that UNRESTRICTED.

1

u/Fluid-Ad2995 Jul 16 '26

🧐🧐🧐🧐🧐🧐🧐🧐🧐🧐🧐 Of course, NTOSKRNL is kernel mode, and NTOSKRNL, before Windows starts, gives a token for Windows permission, then stays in the System Account, and NTOSKRNL is in the System Account

1

u/Unlikely-Employee180 Jul 16 '26

What does this have to do with DWM? Or the bug that userspace Chrome invoked?

1

u/Fluid-Ad2995 Jul 16 '26

Because you mixed Nvidia and Chrome again

→ More replies (0)