fidzu : computers

"I didn't think a rock like this existed on Earth," a geologist at the Lunar and Planetary Institute in Texas told the Washington Post. It looks like a polished rock, dark brown with a clay-colored stripe - but it's actually one of the oldest Mars meteorites ever found, blasted by an impact from the surface of Mars billions of years ago: Technically speaking it's a collection of eight rock fragments, the largest of which is about the size of a fist. Nearly two pounds of the meteorite was discovered in the Sahara in Mali in 2022, and most is now held by a museum in Maine. Within two years, an initial examination determined the meteorite hailed from Mars; scientists are now finally digging deeper, with stunning results. It offers records of "interactions of water and rock and maybe even an imprint of the Martian atmosphere as it was losing water," says Lee Saper, co-author of a new paper recently published in Science. "It was only after we started looking closely that we realized this meteorite is really unique," said Yang Liu of NASA's Jet Propulsion Laboratory in Southern California, the lead author of a new paper published in Science. "One of the paper's reviewers called it a Rosetta Stone for Mars." Its mix of minerals "tells a story about how the planet's crust formed from cooling magma before it was eventually altered by subsurface water," NASA's JPL says in an announcement. The Washington Post reports: The story begins 4.1 billion years ago, when crystals of a mineral called zircon probably solidified out of molten magma on Mars. "That was a game changer," [said Yang Liu, a planetary scientist at NASA's Jet Propulsion Laboratory in California], since scientists can date zircon very precisely, and it has been rare in other Mars meteorites. The date immediately put the Teghaza meteorite on special footing, alongside only two other Mars rocks known to have formed by 4 billion years ago... Perhaps most intriguingly, the researchers also saw signs that the rock had been exposed to water during its evolution, a find detailed in work published this summer in Science Advances.

Read more of this story at Slashdot.

07 Nov 2026 7:00pm GMT

Despite the Trump administration's efforts to halt development on a $6.2 billion wind farm, it's now "completely up and running," reports the nonprofit energy news site Canary Media, delivering enough electricity to power the equivalent over 350,000 homes: On Thursday, the Danish energy giant Ørsted said its 704-megawatt wind farm near Connecticut and Rhode Island began "generating up to its full capacity" in October. Revolution Wind began producing smaller amounts of power in the spring, and the company installed the last of 65 turbines in September. The project is the third U.S. utility-scale offshore wind farm to reach full commercial operations, after South Fork Wind near New York and Vineyard Wind near Massachusetts. Before the start of Trump's second term, BloombergNEF projected America would build 39 gigawatts of offshore wind by 2035 the article points out, but "Now, it expects just 5.9 GW to come online - an amount that reflects the handful of projects that were already completed or under construction at the start of last year." Despite the diminished pipeline, the carbon-free energy source is still expected to help keep household utility bills in check across the U.S. Northeast, experts say. Revolution Wind and the country's other completed projects have already played a key role in reducing grid stress during extreme weather events this year... Ørsted hit its power milestone despite being forced to halt construction twice last year. In August 2025, the Interior Department issued a stop-work order for Revolution Wind, due to unspecified national security threats. That order was tossed out by a federal judge one month later. But in late December, the administration issued new stop-work orders to all five offshore wind projects then under construction. Judges struck those orders down one by one - but not before developers had lost huge sums of money and nearly missed key project deadlines... Meanwhile, Ørsted said it's making progress on another offshore wind development, Sunrise Wind. The developer on Thursday said it has finished installing all of the wind-turbine foundations for the 924-MW project off the coast of Long Island, New York. That installation is expected to be fully operational in the second half of next year.

Read more of this story at Slashdot.

07 Nov 2026 6:00pm GMT

"AlmaLinux OS charted a new path in 2023 when Red Hat restricted source code access to Red Hat Enterprise Linux," remembers Linux Magazine. "Rather than pursue 1:1 compatibility with RHEL like other Enterprise Linux alternatives, the AlmaLinux OS Foundation chose application binary interface (ABI) compatibility, which guarantees that applications and kernel modules that work on RHEL will work on AlmaLinux OS." No longer constrained by the 1:1 promise, AlmaLinux can offer new features, or add back deprecated ones, while still remaining a stable, drop-in replacement for RHEL... The release of AlmaLinux OS 10.2 in May 2026 reveals just how far AlmaLinux has come.... When RHEL 10 increased the x86-64-v2 architecture baseline to x86-64-v3, many older server platforms (and some new ones) were left in the lurch. These older servers couldn't support the modern CPU feature sets in x86-64-v3, including AVX2 CPU instructions. AlmaLinux recognized that many community members employed older hardware that relied on x86-64-v2. While x86-64-v3 is enabled by default in AlmaLinux OS 10 and AlmaLinux OS Kitten 10, an additional x86-64-v2 build is also available. The x86-64-v2 build works best for environments that rely on standard OS packages or that can rebuild any additional packages required by x86-64-v2. For users with older hardware, the additional x86-64-v2 build allows continued use of current hardware, saving money and keeping servers from the landfill. AlmaLinux OS 10 is actively supported through 2030 with security support through 2035, significantly extending the life of older hardware.... Many legacy applications and containerized workloads still run on i686, a 32-bit computer processor architecture belonging to the Intel x86 family, including software that only ships as i686, CI pipelines that require a specific 32-bit glibc, and seemingly normal looking containers that require a 32-bit environment. RHEL 10 completely removed 32-bit application support and multilib libraries after deprecating support in earlier releases... AlmaLinux OS 10.2 has added package repos and official container images for 32-bit x86 (but not a 32-bit kernel or installer)... NVIDIA GPUs, ubiquitous in modern computing, have been a pain point for Linux users. Getting the closed-source NVIDIA drivers has required extra steps and manual installation. When NVIDIA released an open source version of their graphics driver, AlmaLinux integrated the drivers, along with the associated CUDA components, into the AlmaLinux repository starting with AlmaLinux OS 9 and 10. AlmaLinux also signs the open source drivers, allowing secure boot with the NVIDIA drivers they ship. Unlike RHEL users, AlmaLinux users now have native support, allowing them to skip manual installation. AlmaLinux users can now enjoy a fully integrated NVIDIA experience. In addition, "Thanks to ABI compatibility, AlmaLinux can sometimes deliver patches more quickly than RHEL," the article points out. And it lists other points where AlmaLinux OS 10.2 diverges from RHEL 10: Re-enabling frame pointers disabled by default in RHEL and CentOS Stream to provide system-wide, real-time tracing and profiling to diagnose and optimize code. Enabling both kernel and userspace components that allow installation of AlmaLinux on a Btrfs filesystem Adding SPICE support dropped in RHEL 9, allowing users to interact with a virtual machine's desktop remotely instead of just from the host server. Restoring support for older storage and network drivers disabled upstream, including Adaptec, Dell PERC, HP, Mellanox, QLogic, Emulex, LSI, and Broadcom.

Read more of this story at Slashdot.

07 Nov 2026 5:00pm GMT

Genes and archaeology are revealing how Bantu speakers spread across much of Africa.

07 Nov 2026 12:15pm GMT

Soldier told repeatedly to lock down devices before deploying, got sextorted, court-martialed.

07 Nov 2026 11:00am GMT

It's the exact path, not the apparent severity that matters most, doctors say.

06 Nov 2026 11:09pm GMT

Ubuntu has been at the forefront of replacing the traditional versions of basic tools like sudo with replacements written in Rust, but aside from worries about replacing battle-tested code with brand new, relatively untested code, there's new things to worry about it. As it turns out, sudo-rs, the Rust replacement for sudo, is intentionally incompatible with the classic version in dangerous ways, as Chris Siebenmann discovered to his dismay. Basically, the classic sudo supports the use of wildcards defined using square brackets, so that if you allow a user to run, say, /usr/sbin/exim -bp, without a password, they can run exim -bpa, exim -bpc, exim -bpr, or exim -bpu without having to supply a password. This allows for very specific, fine-grained access control, which is quite a nice capability to have if you're managing many systems and users. Sadly, sudo-rs intentionally does not support this, opting to only allow you to use the generic * wildcard. Worse yet, it doesn't really make this clear, either. ↫ Chris Siebenmann I do not really have words for this. The Rust sudo has apparently opted to keep the single most dangerous wildcard while disallowing all of the wildcards that allow one to be narrow and specific about what you're allowing, and it buries this at the end of a section that devotes a bunch of words to describing functionality it doesn't have and doesn't support, with absolutely nothing else in that section to say this (either up front or in the descriptions of how all the wildcards would work if sudo-rs supported them, which it doesn't). If you're going to replace such vital, core tools like sudo that god knows how many people rely on every single day, you better be damn sure you're feature-complete and can act as a drop-in replacement. If someone switches from sudo to doas, nobody expects the experience to be identical. However, if you're consistently being told that sudo-rs is a drop-in replacement and you shouldn't expect any disruptions, you better be able to make true on that promise. Ubuntu isn't some also-ran small hobby distribution, and its developers should act like it. What a clown show.

05 Nov 2026 4:24pm GMT

The second desktop environment release I've got for you today is LXQt 2.5.0. This new version excises its last LXDE dependency, and QTerminal and QTermWidget received considerable improvements, like new background image modes, a visual bell, support for OSC-8 hyperlinks, and more. There's a ton of smaller changes and improvements as well, but do note that due to a bug, 2.5.0 broke LXQt's Monitor Settings on X11. The project intends to fix this as quickly as possible and push a point release to address this issue.

05 Nov 2026 4:03pm GMT

It's desktop environment Thursday, as I've got two new releases for you today. First, Cinnamon, the desktop environment primarily associated with Linux Mint, has hit version 6.8. This version will officially ship with Linux Mint 27, scheduled for around Christmas of this year. Highlights of Cinnamon 6.8 include hibernation support via a Suspend action in the main menu, modern one-to-one trackpad gestures for both Wayland and Xorg sessions, support for the oo7 Secret Service provider, support for multiple instances in the Sound applet, and a more unified Network applet that merges the WireGuard and VPN sections. ↫ Marcus Nestor at 9To5Linux While Cinnamon is first and foremost a Linux Mint project, it's available on countless other distributions as well, including dedicated variants for popular distributions like Fedora and Ubuntu. Its Wayland support is finally materialising too, which is long overdue.

05 Nov 2026 3:57pm GMT

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

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

Good morning from JetBrains Berlin office!

01 Jun 2026 12:00am GMT