Agreguesi i feed

In an Amazon News blog post, their HR leader describes using AI to write 100,000 lines of code — 25 years after she last coded. "Do you know how empowering it is to realize that after 25 years away from coding, you can actually build again?" First she built a calendar app for her family, but then used Amazon's AI-powered coding tool Kiro to write an app for Amazon's internal "Everyone Can Build" event. We opened the competition to every employee on our team, and within just a few weeks, more than 1,500 people were building. I couldn't believe what they built. One employee built an app that turned a nearly four-hour manual process into a one-second automated check, saving tens of thousands of hours annually. Another made a desktop pet named Momo that keeps your tasks, reminders, and shortcuts a click away. Since then, I've written over 100,000 lines of code with AI. What I've found is that the more you work with these tools, the more natural the process becomes, and the more you realize they're expanding what you're capable of, not replacing it. You don't need perfection to start. You just need to dive in. When I decided to build the submission app for our team competition, I didn't know how to begin, so I asked our internal AI workplace assistant, called Aza. It pointed me to the right tools and helped me take the first step. From there, I opened Kiro and started building. When you give employees the ability and tools to solve problems themselves, they will surprise you with what they create... At Amazon, every employee has access to AI tools. Whether someone needs a quick answer, wants to move faster in their day-to-day, or is ready to try building something new, the resources are there. The more people use these tools, the more capable they become with them, and that experience carries forward in their careers... We also want to make it easy for people to build credentials that are recognized across industries. That's why AI training is free for every Amazon employee. Amazon covers the full cost of one AWS AI certification exam per year, with options ranging from foundational AI concepts to professional-level generative AI. Employees can choose the path that fits where they are in their learning journey. Long-time Slashdot reader theodp notes that 7 months ago Galetti also took to Amazon News to announce the elimination of 16,000 corporate jobs, a move which CNBC noted coincided "with a push to invest heavily in artificial intelligence." The job reductions come just a few months after October's layoffs, when 14,000 employees were let go across Amazon's corporate workforce. At the time, the company indicated the cuts would continue in 2026 as it found "additional places we can remove layers."

Read more of this story at Slashdot.

"Multikernel Technologies has put out mklinux v7.0-mk2, the first public release of the multikernel Linux tree it's been building since last year," reports the blog It's FOSS: The basic premise of the project is that one physical server can run several independent Linux kernels side by side, each with its own dedicated CPUs and memory. So, the same box could run a database on one kernel and a GPU training job on another without either kernel touching the other's resources... One kernel runs as the host, controlling the machine's CPUs, memory, and PCI devices. When it spins up a new kernel instance, that instance gets its own dedicated slice of hardware and boots straight onto it using Linux's kexec mechanism, running natively rather than under a hypervisor. The host tracks all of this through device tree overlays under /sys/fs/multikernel/, and it can shift hardware between running instances while everything stays up. That's a different setup from both VMs and containers. A VM still puts a hypervisor and a host kernel between the app and the hardware. A container skips the hypervisor, but every tenant on the machine shares one kernel... This release only supports x86_64 hardware, though Multikernel Technologies says the architecture-specific code is already modular enough for other ports to follow later. The article notes they're selling multiple products based on the kernel tree, including one for running AI agents in their own kernel with direct GPU access and one that promises to patch a running kernel without taking the system down.

Read more of this story at Slashdot.

From the gaming news site Aftermath" Game developer and consultant Ryan Laley traveled to Cologne, Germany from Essex, England to showcase his upcoming horror social deduction game Mimic at the annual Gamescom event. He paid "thousands of pounds" to get a booth at the show, where other game developers and press could try the game ahead of its October release. But Laley's Gamescom was cut short when he realized Friday morning that his brand new Alienware laptop, purchased for the event, was missing. The laptop was stored in a cupboard in the booth, and Laley started asking nearby vendors to see if someone had moved it. That's when he realized it was stolen — and that he wasn't alone. Laley's booth in Gamescom's business area, specifically in the International Game Developers Association Lounge, had been hit in what appears to be a string of thefts at the convention center. The business area of the convention is not open to the public, only press and others with specific tickets. Laley said Gamescom advertised this area as having 24/7 security and limited access after hours... Publisher and merchandiser iam8bit, in a nearby booth showcasing Escape Academy 2: Back 2 School and Petal Runner, had two laptops with game builds stolen Thursday night from its booth, a representative confirmed to Aftermath. "Meanwhile, Tessera Studios had two laptops and a Steam Deck taken from its cabinet," reports Tom's Hardware: Gamescom organizers responded to the issues, saying that although they have arranged for uniformed guards to provide general security, individual booth security must be booked separately. They've also advised exhibitors to have insurance against theft, and said these warnings are noted in the terms and conditions for participants, as well as in the event's technical guidelines. "All cases have been reported to us and to the police, and investigations are already underway," the organizers' statement read. They also said that security is one of their priorities at the event, but also added, "At an event of this size, however, there will always be individuals attempting to take advantage of the situation."

Read more of this story at Slashdot.

The Debian Long Term Support (LTS) Team hereby announces that Debian 11 bullseye support has reached its end-of-life today, 31 August 2026, five years after its initial release on 14 August 2021.

Version:7.3-rc1 (mainline) Released:2026-08-30 Source:linux-7.3-rc1.tar.gz Patch:full

Some time ago I visited a used book fair and came across this awesome piece of 80s scifi-asthetic.

This book is a collection of short stories by the Polish author Stanisław Lem originally published in 1964. Its English title is The Cyberiad. One story, about Trurl's electronic troubadour, turned out to be surprisingly topical.

Spoilers for the whole story follow

The inventor Trurl (revealed in other stories to be a robot) wants to create a machine that can generate poetry. He begins by obtaining several hundred tonnes of books to use as training data.

Trurl gets to work constructing the electric poetry machine. In the process they have to create massive data storage containers that stretch further out than one can see using binoculars. This is considered a necessary evil to get this great invention going.

The machine will not work as expected. As a last resort Trurl rips out all logic circuits and replaces them with "narsistors". Then things start working.

Trurl invites his friend Klapaucius over to test the new machine. They give it all sorts of weird and wacky instructions like "create a pastoral love poem that also contains mathematics and cybernetics". Basically they do a whole bunch of prompt engineering. They talk and behave exactly like people of 2021-2023 did when LLMs first appeared.

Eventually the machine causes uproar among poets and there are protests demanding it to shut down. These go nowhere in part because the media secretly love the machine. They are using it to create their own content for pennies and thus don't want to see it come to harm. As all of this is going on various people develop symptoms quite similar to modern day AI psychosis.

Things eventually crash when Trurl gets the machine's electrical bill, which turns out to be astronomical. He needs to get rid of the machine and manage to dump it on a visiting dignitary who takes it to his home planet where causes a supernova explosion. Trurl deems that to be sufficiently far away to not be his problem any more.

The difference between fact and fiction

In the story all the problems are caused by the fact that the machine's output is vastly higher quality than anything humans can create. Even the great Stanisław Lem could not predict that in reality the output would turn out to be mediocre garbage and still lead to all the same problems.

Even though the story specifies that the machine is given some "basic instructions" first, nobody tries to do a prompt injection attack on it. That would only appear almost 30 years later in 1993's Paranoia novel Title Deleted for Security Reasons. An earlier example may well exist somewhere, it almost always does.

A Kubernetes workload can run with more Linux capabilities than its code needs. When capability settings are missing or broad, that excess authority may remain invisible because the application still works.

Removing a Linux trace instance should end its lifetime. An open tracefs reader can currently keep using that instance after another task removes it, creating a kernel use-after-free path in the tracing subsystem.

A Linux service may need broad system-call access while it starts, then only a smaller set while it handles requests. A single policy loaded before startup often has to keep every required call available for the service's entire lifetime.

Version:7.2.2 (stable) Released:2026-08-28 Source:linux-7.2.2.tar.xz PGP Signature:linux-7.2.2.tar.sign Patch:full (incremental) ChangeLog:ChangeLog-7.2.2

Version:7.1.12 (stable) Released:2026-08-28 Source:linux-7.1.12.tar.xz PGP Signature:linux-7.1.12.tar.sign Patch:full (incremental) ChangeLog:ChangeLog-7.1.12

Version:6.18.48 (longterm) Released:2026-08-28 Source:linux-6.18.48.tar.xz PGP Signature:linux-6.18.48.tar.sign Patch:full (incremental) ChangeLog:ChangeLog-6.18.48

Version:6.12.107 (longterm) Released:2026-08-28 Source:linux-6.12.107.tar.xz PGP Signature:linux-6.12.107.tar.sign Patch:full (incremental) ChangeLog:ChangeLog-6.12.107

Version:6.6.155 (longterm) Released:2026-08-28 Source:linux-6.6.155.tar.xz PGP Signature:linux-6.6.155.tar.sign Patch:full (incremental) ChangeLog:ChangeLog-6.6.155

Version:6.1.186 (longterm) Released:2026-08-28 Source:linux-6.1.186.tar.xz PGP Signature:linux-6.1.186.tar.sign Patch:full (incremental) ChangeLog:ChangeLog-6.1.186

Version:5.15.219 (longterm) Released:2026-08-28 Source:linux-5.15.219.tar.xz PGP Signature:linux-5.15.219.tar.sign Patch:full (incremental) ChangeLog:ChangeLog-5.15.219

Version:5.10.268 (longterm) Released:2026-08-28 Source:linux-5.10.268.tar.xz PGP Signature:linux-5.10.268.tar.sign Patch:full (incremental) ChangeLog:ChangeLog-5.10.268

Together with Modal, I’m happy to announce that the Sovereign Tech Agency is investing nearly €510k into Flatpak development. The focus is on closing gaps in Flatpak’s sandboxing story: new portals for audio, networking, VPNs, and spell checking, plus infrastructure work on entitlements and intents.

I’ll be leading the technical side alongside Adrian, with organizational support from Kateryna and Cade. We’ve brought on a great team and the project will ramp up over the coming months through the end of 2027.

Read the full announcement on the Modal blog.

Patch work often gets declared finished at the package manager. The update installs, version inventory changes, the service restarts, and the ticket begins moving toward closed. That sequence is clean. Production rarely is.

In Some Changes to GNOME Security Tracking, I reported:

I will discontinue tracking newly-reported security issues on November 1, 2026. During November, I will focus only on tracking issues reported prior to November 1. By December 1, all disclosure deadlines for that set of issues will have been reached, and I will be done.

This is because I was planning to leave my job at Red Hat on December 31 due to some internal Red Hat policy changes. But this timeline has now unexpectedly moved forward two months, to October 30. Accordingly, I will now discontinue tracking newly-reported security issues on October 1, 2026. During October, I will focus only on tracking issues reported prior to October 1. By November 1, all disclosure deadlines for that set of issues will have been reached, and I will be done.