Rivers of Lava on Venus Reveal a More Volcanically Active Planet

Witnessing the blood-red fires of a volcanic eruption on Earth is memorable. But to see molten rock bleed out of a volcano on a different planet would be extraordinary. That is close to what scientists have spotted on Venus: two vast, sinuous lava flows oozing from two different corners of Earth’s planetary neighbor. From a report: “After you see something like this, the first reaction is ‘wow,'” said Davide Sulcanese, a doctoral student at the Universita d’Annunzio in Pescara, Italy, and an author of a study reporting the discovery in the journal Nature Astronomy, published on Monday. Earth and Venus were forged at the same time. Both are made of the same primeval matter, and both are the same age and size. So why is Earth a paradise overflowing with water and life, while Venus is a scorched hellscape with acidic skies?

Volcanic eruptions tinker with planetary atmospheres. One theory holds that, eons ago, several apocalyptic eruptions set off a runaway greenhouse effect on Venus, turning it from a temperate, waterlogged world into an arid desert of burned glass. To better understand its volcanism, scientists hoped to catch a Venusian eruption in the act. But although the planet is known to be smothered in volcanoes, an opaque atmosphere has prevented anyone from seeing an eruption the way spacecraft have spotted them on Io, the hypervolcanic moon of Jupiter. In the 1990s, NASA’s spacecraft Magellan used cloud-penetrating radar to survey most of the planet. But back then, the relatively low-resolution images made spotting fresh molten rock a troublesome task.

Read more of this story at Slashdot.

Intel Removes Knights Mill and Knights Landing Xeon Phi Support In LLVM 19

Memory Sealing ‘mseal’ System Call Merged For Linux 6.10

“Merged this Friday evening into the Linux 6.10 kernel is the new mseal() system call for memory sealing,” reports Phoronix:

The mseal system call was led by Jeff Xu of Google’s Chrome team. The goal with memory sealing is to also protect the memory mapping itself against modification. The new mseal Linux documentation explains:

“Modern CPUs support memory permissions such as RW and NX bits. The memory permission feature improves security stance on memory corruption bugs, i.e. the attacker can’t just write to arbitrary memory and point the code to it, the memory has to be marked with X bit, or else an exception will happen. Memory sealing additionally protects the mapping itself against modifications. This is useful to mitigate memory corruption issues where a corrupted pointer is passed to a memory management system… Memory sealing can automatically be applied by the runtime loader to seal .text and .rodata pages and applications can additionally seal security-critical data at runtime. A similar feature already exists in the XNU kernel with the VM_FLAGS_PERMANENT flag and on OpenBSD with the mimmutable syscall.”
The mseal system call is designed to be used by the likes of the GNU C Library “glibc” while loading ELF executables to seal non-writable memory segments or by the Google Chrome web browser and other browsers for protecting security sensitive data structures.

Read more of this story at Slashdot.

Technical Issues’ Stall MLB’s Adoption of Robots to Call Balls and Strikes

Will Major League Baseball games use “automated” umpires next year to watch pitches from home plate and call balls and strikes?
“We still have some technical issues,” baseball Commissioner Rob Manfred said Thursday. NBC News reports:

“We haven’t made as much progress in the minor leagues this year as we sort of hoped at this point. I think it’s becoming more and more likely that this will not be a go for ’25.”

Major League Baseball has been experimenting with the automated ball-strike system in minor leagues since 2019. It is being used at all Triple-A parks this year for the second straight season, the robot alone for the first three games of each series and a human with a [robot-assisted] challenge system in the final three.

In “challenge-system” games, robo-umpires are only used for quickly ruling on challenges to calls from human umpires. (As demonstrated in this 11-second video.)

CBS Sports explains:

Each team is given a limited number of “incorrect” challenges per game, which incentivizes judicious use of challenges… In some ways, the challenge system is a compromise between the traditional method of making ball-strike calls and the fully automated approach. That middle ground may make approval by the various stakeholders more likely to happen and may lay the foundation for full automation at some future point.

Manfred cites “a growing consensus in large part” from Major League players that that’s how they’d want to see robo-umpiring implemented, according to a post on X.com from The Athletic’s Evan Drellich. (NBC notes one concern is eliminating the artful way catchers “frame” caught pitches to convince umpires a pitch passed through the strike zone.)

But umpires face greater challenges today, adds CBS Sports:

The strong trend, stretching across years, of increased pitch velocity in the big leagues has complicated the calling of balls and strikes, as has the emphasis on high-spin breaking pitches. Discerning balls from strikes has always been challenging, and the stuff of the contemporary major-league pitcher has made anything like perfect accuracy beyond the capabilities of the human eye. Big-league umpires are highly skilled, but the move toward ball-strike automation and thus a higher tier of accuracy is likely inevitable. Manfred’s Wednesday remarks reinforce that perception.

Read more of this story at Slashdot.