https://www.theregister.com/2025/01/14/microsoft_linux_change_pulled/
We're only here to help... The good news is when vallor, with his thing about kernels, builds 6.13 it won't blow up.
On 15 Jan 2025 01:04:32 GMT, rbowman <bowman@montana.com> wrote in <luofsuF6gdtU3@mid.individual.net>:
https://www.theregister.com/2025/01/14/microsoft_linux_change_pulled/
We're only here to help... The good news is when vallor, with his
thing about kernels, builds 6.13 it won't blow up.
And I booted the latest rc kernel just yesterday. I guess I'm running
the dodgy Microsoft code(!).
Pardon me, while I go boot the release Linux, 6.12.9. (Incidentally,
I've noticed Fedora stays one release behind the current release -- is
that on purpose?)
https://www.theregister.com/2025/01/14/microsoft_linux_change_pulled/
We're only here to help... The good news is when vallor, with his thing about kernels, builds 6.13 it won't blow up.
rbowman wrote this post while blinking in Morse code:
https://www.theregister.com/2025/01/14/microsoft_linux_change_pulled/
We're only here to help... The good news is when vallor, with his
thing about kernels, builds 6.13 it won't blow up.
The word "pulled" in the URL is... unfortunate.
https://www.theregister.com/2025/01/14/microsoft_linux_change_pulled/
"Petkov will not be the only one wondering how the change made it in without a review by the Linux x86/x86_64 maintainers."
Moles among Linux developers, probably?
This was also one of the Capone style methods in the 1920s to get rid of their competitors.
Mr. Windows, it seems, is practicing it too.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 546 |
Nodes: | 16 (1 / 15) |
Uptime: | 160:10:20 |
Calls: | 10,385 |
Calls today: | 2 |
Files: | 14,056 |
Messages: | 6,416,492 |