22 Nov 2026
Slashdot
Climate Change Talks Fall Apart In Final Hours Over Fossil Fuels
NPR reports international climate talks "broke down in overtime hours, over the main cause of planetary warming - fossil fuels." At Sunday's U.N. climate summit, "nearly 200 countries failed to reach an agreement on whether they should move away from energy sources like coal and natural gas." The talks ended in a dramatic fashion, with the European Union negotiators saying they could not agree to a final agreement without mentioning the transition away from fossil fuels - the primary driver of climate change. The EU bloc then walked out of the room... After representatives of the EU walked out, other countries also objected - including Panama and island states such as the Marshall Islands. The European climate chief, Wopke Hoekstra, said that when the world is heading for an overshoot of 1.5 degrees, the EU could not tolerate an agreement that does not mention fossil fuels. "That is not acceptable," Hoekstra told reporters after walking out of the talks. "We do that with a heavy heart with many other countries, but we simply cannot accept this." "Burning fossil fuels like oil, gas and coal make up roughly 73% of global emissions," the article notes, adding this is the first U.N. climate summit with a scientific consensus that the planet has already warmed past the threshhold countries agreed not to pass in 2015 of 1.5 degrees Celsius (2.7 degrees Fahrenheit).
Read more of this story at Slashdot.
22 Nov 2026 6:41pm GMT
How Does GTA 6 Depict Electric Cars?
Grand Theft Auto 6 as seen by the EV news site Electrek: GTA works as a mirror. In 2013, the EV was a punchline: a Tesla parody that overheated if you drove it too fast. In 2026, it's just another car in Vice City traffic, and the joke is on the guy in the pickup parked in the charging stall. That's a good sign of where EVs actually are. Satire goes after what's common, and Rockstar decided EVs are common enough to be part of everyday Leonida, more so in the city than in the Keys, just like real life. And that message is reaching a huge audience... Tens of millions of people are now driving EVs that charge as fast and as cheaply as gas cars, with no range anxiety. No automaker ad campaign gets close to that. They point out GTA 6 is "the first mainline GTA where energy matters." Gas cars burn fuel and need a pump, and EVs have a battery level and need a plug. Rockstar could have used that to make EVs a pain. It didn't. In my testing, the EVs have about the same range as the gas cars, charge just as fast as a fill-up, and cost the same or less to top up. Kotaku's range test backs that up. On the same highway loop, a Tesla Model 3 lookalike lasted 20 minutes and 23 seconds on a charge, longer than the Banshee sports car at 18 minutes and 31 seconds, and not far off an old pickup at 29 minutes and 8 seconds. Crossing the whole map by highway takes under 15 minutes, according to Kotaku. And finding a charger isn't a problem. Wccftech counted 120 EV chargers marked on the map, against just 57 gas stations... GTA has always been a parody of American life. With EVs, it's now slightly ahead of it. Florida is one of the strongest EV markets in the country, with a 9.4% share of new passenger vehicle sales in Q2 2026 versus 7.4% nationally, according to the Southern Alliance for Clean Energy.. But real Florida still has roughly three gas stations for every public charging location, based on the Alliance for Automotive Innovation's count of 3,267 charging locations and xMap's count of more than 10,500 gas stations. Leonida flips that ratio. GTA 6's Vice City has public fast chargers - branded "ReVolt America," which Electrek calls "an obvious copy of Electrify America's stations." And Electrek also spotted a giant charging hub at a power plant "with dozens of stalls and several EVs plugged in." There's even EV chargers being blocked by gas-powered cars, a phenomenon Electrek first covered in 2019
Read more of this story at Slashdot.
22 Nov 2026 5:34pm GMT
Python Devs Document 'De-fanging Dangerous Triggers In GitHub Actions'
"A handful of GitHub Actions triggers let a stranger on the internet start a workflow that may have access to your secrets," warn two security developers at the Python Software Foundation. Have dangerous triggers caused real incidents? Yes, repeatedly... The maintainers behind these projects weren't careless. These triggers look harmless in a workflow file, and the unsafe version is one line away from the safe one... When someone opens a pull request from a fork, the pull_request trigger runs their code with a read-only token and no secrets. That's the safe one. pull_request_target looks almost the same in a workflow file and behaves very differently. It runs with a read/write token and access to your repository and organization secrets. GitHub built it for chores like labeling pull requests from forks, where the workflow never touches the contributor's code. The trouble starts when a workflow checks out the pull request and runs it anyway... Anyone with a GitHub account can open that pull request. Their code now runs with your credentials. This is called a "pwn request", and GitHub's docs describe it as the root cause of multiple supply-chain compromises. The issue_comment trigger carries the same risk. This trigger fires when anyone comments on an issue or pull request, and the workflow runs with the repository's token and secrets... Sometimes the workflow pastes the comment text into a templated shell command, and the comment turns out to inject different instructions into the workflow shell. Python's official security developer in residence Seth Larson joined PyPI safety/security engineer Mike Fiedler to remove these dangerous trigger, also applying the policies Python Software Foundation-stewarded GitHub organizations (psf, python, and pypi). "They also wrote up technical documentation on how to roll these policies out to your own projects and organizations. "On a GitHub Team or Enterprise plan, you can turn them off for every repository in your organization with one policy. On a Free plan, you can do it one repository at a time. Set the policy up, check what it would block, then enforce it."
Read more of this story at Slashdot.
22 Nov 2026 4:34pm GMT
21 Nov 2026
OSnews
Dual boot NetBSD 11.1 and Debian 13 on a ThinkPad T14 G1
Sometimes, all you need is a well-written guide on dual-booting NetBSD and Linux. After gaining some confidence from installing NetBSD on my Raspberry Pi, I started wondering, what if I installed it on my daily-driver ThinkPad and set it up to dual-boot? I could use NetBSD for whatever I felt like and fall back to Linux whenever I needed to. ↫ neongod So that's exactly what you're getting.
21 Nov 2026 11:52pm GMT
20 Nov 2026
OSnews
The history behind the x86 CPU: from 4004 to 486
Why is x86 little-endian? Why are the registers called AX, BX, CX, and DX? Why do DOS programmers write addresses like A000:0000, and why does a modern PC still wake up pretending to be a chip from 1978? The answers are not in the datasheets. They are in the story of how each chip was born. ↫ Gustavo Pezzi The x86 is like an archaeological dig site that's been dug in the 1800, before modern standards of dig sites were established to preserve context.
20 Nov 2026 10:20am GMT
FreeBSD GUS: RCU’s cool cousin
FreeBSD has a pretty neat safe memory reclamation scheme (something akin to RCU), that's also been adopted by XNU that hasn't really been well-documented outside of code comments, and I thought it would've been interesting to write about it. ↫ Loïc Grégoire Some light reading for the weekend.
20 Nov 2026 10:09am GMT
16 Nov 2026
Planet Arch Linux
Mutex poisoning is not for everyone
After some recent discussion on the topic of mutex poisoning and notably a blog post that I thought was interesting, thoughtful, exhaustive, yet completely disagreed with, I wanted to comment on the debate myself. To me, poisoning-by-default is one of biggest mistakes that were made in the language, next to some others that are a story for a different time.
16 Nov 2026 12:00am GMT
08 Oct 2026
Planet Arch Linux
Writing parsers is hard
This is a story of how we got from something like this: Failed to deserialize BUILDINFO file: Parser failed with the following error: unknown ^ invalid makepkg build environment option expected `buildflags`, `ccache`, `check`, `color`, `distcc`, `sign`, `makeflags` To this: When the ALPM project started, the goal was fairly simple: Better tooling to interact with the low-level plumbing of Arch Linux Package Management (ALPM). This meant binaries to read/write individual file types, better error messages, extensive specifications and of course exports to common dataformats like JSON. The thing is, although some of us already had experience with low-level dataframe parsing, …
08 Oct 2026 12:00am GMT
09 Aug 2026
Planet Arch Linux
On scripts and hooks
Over the last few weeks, we have been doing research on the integration of our official distribution packages when installed on a target system. In this context we have been looking at the current uses of alpm-install-scriptlet(5) files and alpm-hooks(5) in around 120 package source repositories (alpm-source-repo(7)) to better understand the underlying functionality and use-cases these two integrations offer and target. In this article we are going to look at how these two systems work, how Arch Linux is currently using them and attempt to provide suggestions for when to use which. Learning about alpm-hooks(5) and alpm-install-scriptlet(5) files …
09 Aug 2026 12:00am GMT