Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.os.linux.advocacy > #684138

Re: Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code change

From Physfitfreak <physfitfreak@gmail.com>
Newsgroups comp.os.linux.advocacy
Subject Re: Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code change
Date 2025-01-16 11:29 -0600
Organization Modern Human
Message-ID <vmbflv$1ti1$1@solani.org> (permalink)
References <luofsuF6gdtU3@mid.individual.net> <181b2f420a405757$167017$891815$802601b3@news.usenetexpress.com>

Show all headers | View raw


On 1/16/25 7:27 AM, Farley Flud wrote:
> On Wed, 15 Jan 2025 01:04:32 +0000, rbowman wrote:
> 
>> https://www.theregister.com/2025/01/14/microsoft_linux_change_pulled/
>>
> 
> This has got to be one the shittiest articles that I have ever read.
> 
> It has ZERO information.
> 
> After reading this I have no idea what the fuck is going on.
> 
> It concerns, I think, ROX or "read only executable pages" but how
> or what effect they have is never explained.
> 
> The article is pure garbage.
> 
> 



Last sentence:

    "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?

In Iran of Shah's time, when an armed anti-government political group 
formed (many of them sprang up in the last ten years of that regime), 
all SAVAK needed to do to destroy such groups was to create a similar 
one in its proximity.

Then, gradually, this bogus group after some harmless scores, made 
attempts to connect with the real one. After a few months or at most a 
year or two, some connections would get established. Then ideas of 
"joining forces to get stronger" would gradually get brought up until at 
last the two groups joined. Then the silent slaughter would take place.

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.

Back to comp.os.linux.advocacy | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code change rbowman <bowman@montana.com> - 2025-01-15 01:04 +0000
  Re: Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code change vallor <vallor@cultnix.org> - 2025-01-15 01:47 +0000
    Re: Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code change rbowman <bowman@montana.com> - 2025-01-15 06:13 +0000
  Re: Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code change Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-01-15 08:13 -0500
    Re: Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code change vallor <vallor@cultnix.org> - 2025-01-15 14:05 +0000
  Re: Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code change Farley Flud <fsquared@fsquared.linux> - 2025-01-16 13:27 +0000
    Re: Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code change Physfitfreak <physfitfreak@gmail.com> - 2025-01-16 11:29 -0600
      Re: Intel, AMD engineers rush to save Linux 6.13 after dodgy Microsoft code change Farley Flud <fsquared@fsquared.linux> - 2025-01-16 17:52 +0000

csiph-web