01 Nov 2026

feedSlashdot

AI Makes Linux 7.4 Merge Window the Largest in Kernel History

"On a Git commit basis, the Linux 7.4 merge window has been the busiest on record," writes Phoronix," with 19,671 commits since Linux 7.3: As of this morning in Linux Git ahead of v7.4-rc1, the kernel source tree is up to 41,605,120 lines. That's from 5,193,578 blank lines, 4,993,604 lines of comments, and 31,417,938 lines of detected code. Or nearly half a million lines of code added during the Linux 7.4 merge window, ignoring comments and blank lines [as detected by cloc ]. A historical graph of commits shows a clear spike for Linux 7.4, which Phoronix argues shows the definite recent uptick due to AI/LLM activity." With Linux kernel maintainers being "completely overwhelmed" due to both AI generated bug reports and patches/fixes, the Git commit activity has been surging as a result... The upward trend has continued building the past several kernel releases. Typically the merge windows saw 13~14k commits or less and now we are pushing 20k.... Linux 6.14: 10,034 Linux 6.15: 13,568 Linux 6.16: 13,805 Linux 6.17: 12,289 Linux 6.18: 12,910 Linux 6.19: 13,229 Linux 7.0: 12,468 Linux 7.1: 13,963 Linux 7.2: 14,395 Linux 7.3: 16,267 Linux 7.4: 19,671 And "we could still see a few more trickle in today for Linux 7.4 ahead of the expected Linux 7.4-rc1 kernel release later in the day."

Read more of this story at Slashdot.

01 Nov 2026 8:14pm GMT

Which Tech Companies Started Using Trump's Phrase 'Super Intelligence'?

CNBC reports: A month after President Donald Trump ordered that "super intelligence" replace the term artificial intelligence within executive branch departments and agencies, his leading tech allies, Elon Musk and Mark Zuckerberg, followed suit on earnings calls. Their fellow tech CEOs were less eager to do the same... SpaceX and Tesla adhered to Trump's wishes on earnings calls last week after Musk, earlier in October, changed the name of his rocket company's AI division to SpaceXSI. Speaking on Tesla's call about his work on humanoid robots, Musk said, "Some of them look very impressive, but they're not really using any kind of advanced AI or SI." Zuckerberg was equally compliant on Meta's earnings call on Oct. 21, emphasizing his company's "goal of delivering personal superintelligence to everyone." However, Meta was already using the term, having created a unit called Meta Superintelligence Labs last year.... [Some other tech CEOs are holding out.] Amazon CEO Andy Jassy peppered his call with use of "AI" on Thursday, uttering the abbreviation well over a dozen times in his introductory remarks. A day earlier, Microsoft CEO Satya Nadella said one of the company's three points of focus is "designing AI to empower people." And Alphabet CEO Sundar Pichai was seconds into his quarterly earnings commentary when he said the search giant's "AI investments are driving increased usage and overall user growth...." Trump's preferred term is seeping into other correspondence and documents. Microsoft's annual report, filed last week, included eight mentions of "super intelligence," starting at the top of the letter to shareholders... IBM CEO Arvind Krishna, who didn't attend Trump's September lunch, used "SI" alongside "AI" during his company's earnings call last week.... Lip-Bu Tan, CEO of chipmaker Intel, said Thursday the supply shortage the chip industry is navigating has been "driven by the unprecedented demand for super intelligence." Some in the tech industry have been explicit in their support of Trump's terminology ahead of their forthcoming earnings reports next month. Palo Alto Networks CEO Nikesh Arora repeatedly referred to "SI" on CNBC, and posted on X on Sept. 30, "The meeting at the WH on SI was an epic moment...." Like Arora, [Nvidia CEO Jensen] Huang took to X after last month's AI meeting to praise the "White House Accord on Super Intelligence."

Read more of this story at Slashdot.

01 Nov 2026 5:34pm GMT

College Students are Pushing Colleges to 'De-Flock'

Inside Higher Ed reports: In September, Emory University removed a dozen license plate-reading cameras from its campus in Atlanta and declined to renew its contract with Flock Safety, the company that sells and operates the automatic license plate readers and other mass-surveillance technology. For the coalition of Emory students and employees who had spent months pushing the university to "de-Flock," this was a victory... "We made it very clear that these cameras were unneeded surveillance considering we already have regular security cameras," [said Tony Torres, a sophomore biology major]... Through campus protests, petitions, meetings and teach-ins during the spring and summer, DeFlock Emory broadcast their concerns about the devices: Opaque data-sharing agreements could leave undocumented students vulnerable, the cameras could be hacked, institutions could use them to retaliate against student protesters and they could make students who fear being surveilled less likely go to class, see their friends or seek medical attention when they need it. Such concerns aren't unique to DeFlock Emory. College students across the country - including at Indiana University Bloomington, the University of Florida and the University of North Georgia - are mobilizing to de-Flock their campuses. And like Emory, other institutions are nixing their contracts. Cornell University announced last week it had not renewed its contract with Flock Safety and would be removing the cameras. Pennsylvania State University officials also announced earlier this month plans to end their contract with Flock. An Emory spokesperson told Inside Higher Edthat eliminating Flock's cameras "retains institutional control over our safety infrastructure." But the article also includes a quote from media/technology studies professor Torin Monahan at the University of North Carolina at Chapel Hill. He's spoken with campus police officers about how they're using Flock's cameras, and learned police departments have upgraded surveillance efforts in recent years. "They have an elaborate arsenal in place of high-tech surveillance equipment that really seems overpowered for what their day-to-day needs are, and also incredibly expensive."

Read more of this story at Slashdot.

01 Nov 2026 4:34pm GMT

31 Oct 2026

feedArs Technica

Seabirds racing home over the ocean can get jet-lagged

A long flight home from feeding grounds messes with birds' internal clocks.

31 Oct 2026 11:15am GMT

The FDA wants to pull its approval of a drug. It’s not so easy.

The regulator says Tavneos was approved on the basis of manipulated study data. Should patients still have access to it?

31 Oct 2026 11:02am GMT

feedOSnews

Sculpt OS 26.10 releases

Sculpt OS 26.10 brings quite a few new features, like scalable cursors, support for UK keyboards, better webcam support, and more, but the real meat of this release is much tastier. First, Sculpt 26.10 is the first version based on Genode's custom microkernel instead of relying on a 3rd-party kernel. This kernel - designed from the ground up for the needs of Genode and Sculpt OS in particular - is not only more "micro" than any other of the microkernels supported by Genode, it also solves long-standing deficiencies concerning CPU scheduling and kernel-memory management. Sculpt OS finally stands on Genode's own footing! Finally, Sculpt OS 26.10 pays tribute to this year's overall theme of "building bridges" by featuring our software development kit (Goa SDK) running directly on Sculpt OS without virtualization. This entails a wealth of tooling including GCC, Binutils, Git, Sequoia, Expect, Curl, man, Make, and CMake having landed on Genode. Although still young and not time-tested yet, it shows what's possible today and allows us developers to gradually shift more and more development routine into this self-hosted environment, stressing the general-purpose qualities of Genode and motivating further optimizations. ↫ Sculpt OS release 26.10 announcement This new release also completes the transition from XML to Genode's own HID language for configuration, moves from VirtualBox 6 to 7, and upgrades a whole slew of its Linux-based drivers

31 Oct 2026 8:02am GMT

How long do you need to hold down the power button to turn off a PC?

Raymond Chen published another story from the Windows development trenches, this time about what happens when you hold down the power button. If you hold a PC's power button for 12 seconds, it will turn off at the hardware level without notifying the operating system. This is a safety feature so that you can turn of the computer even if the operating system's "Shut down" command isn't working. After eight seconds of the power button being held down, the Windows kernel realizes that the user is trying to do a force-power-off of the system, and it quickly takes a kernel dump that can be uploaded to the Windows Error Reporting service the next time you turn the system on. ↫ Raymond Chen I'm a bit confused by these numbers, because I have never seen a PC take this long to power off when holding down the power button; usually it takes only a few seconds to do so, meaning Windows would never generate said kernel dump. I tried reading through the various ATX specification documents to find more information on this, but then I remembered I'm not an electrical engineer so I have no idea what I'm looking at. The baseline is that ATX always provides standby power to the motherboard, and pressing the power button shorts the power button pin to ground, telling the PSU to power on fully. Pressing the power button if the computer is running tells the operating system to initiate a shutdown (although you can change this behaviour), but if you hold the button down for a certain number of seconds, it forces a power-off. So far, so good; basic information. It seems that the length of time you need to hold down the power button to force a power-off is dependent on the motherboard in question, handled by a microcontroller or some other IC. Virtually every source I can find says this timing is set to about 4-5 seconds, which is quite a bit shorter than the number of seconds given by Chen. Perhaps motherboard manufacturers consider the 12 seconds to be too long, and just do their own thing, regardless what the ATX specification suggests? What further complicates matters is that Chen details how the kernel dumps created after pressing the power button for 8 seconds do, in fact, get sent to Microsoft once the computer turns on again. In fact, he is one of the people who gets to see these dumps and respond to them, so obviously they are indeed rolling in. Does this mean there's a huge number of computers out there that require you to hold down the power button for 12 seconds to force a shutdown that nobody's ever seen? These emergency kernel dumps are internally classified as "long power button hold" (LPBH) failures. One of the pieces of information recorded in these emergency kernel dumps is whether the screen consists entirely of black pixels. Those failures are sub-classified as "black screen LPBH", and they go to a special virtual team for analysis. (I happen to be a member of this black screen LPBH team.) ↫ Raymond Chen What's going on here? Obviously, I'm not going to doubt Chen, so there must be something here I don't quite understand or that I'm missing. The ATX specification might suggest 12 seconds, but could Windows perhaps adapt its kernel dump behaviour - dumping much sooner than 8 seconds - based on the motherboard it's running on, maybe through information provided by the chipset drivers? I would love it if someone more knowledgeable than me can help us unravel this small mystery.

31 Oct 2026 7:54am GMT

How curl was accidentally Turing-complete for nine months

From curl 8.12 through 8.16, config files could slice variable values and include other config files without an explicit depth cap. Together, these features let curl simulate any two-counter Minsky program. Under the usual idealization of unbounded strings and resources, this construction was Turing-complete. Curl 8.17.0 added a five-level include cap that breaks this reduction. ↫ Nicolas Seriot Neat.

31 Oct 2026 7:10am GMT

feedArs Technica

Once again, NASA is asking for ideas to rescue Hubble from certain death

The space agency solicited ideas for reboosting Hubble four years ago, but they didn't go anywhere.

31 Oct 2026 12:07am GMT

08 Oct 2026

feedPlanet 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

feedPlanet 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

01 Jun 2026

feedPlanet Arch Linux

Today is my first day at JetBrains

Good morning from JetBrains Berlin office!

01 Jun 2026 12:00am GMT