16 Nov 2026

feedSlashdot

Purism Announces 'Librem 5 v2' Linux Phone with RISC-V SoC

From the Linux-news blog OMG Ubuntu: Purism is crowdfunding a new version of its Librem 5 Linux smartphone, this one powered by RISC-V rather than Arm. Librem 5 v2 will use an octa-core SpacemiT K1 RISC-V SoC, replacing the quad-core Arm64 NXP CPU. This processor shift will provide better performance and longer battery life than the original Librem 5 and not run as hot in use. Memory is bumped to 8 GB RAM, up from 3 GB, and storage leaps to 128 GB from 32 GB. Librem 5 v2 will run PureOS, Purism's Debian-based operating system using Phosh as its UI. SD card read speeds are faster, which is handy since the device can boot a second OS from a memory card. On-board hardware encoding means the Librem 5 will be able to take 13 megapixel photos and shoot high-definition video for the first time.... "RISC-V is the future, and Librem 5 v2 is the perfect product to bring it to a mainstream audience", Jonathon Hall, CTO at Purism, says of the launch. "Freeing us from the control of Big Tech starts with the foundation, and RISC-V's foundation frees us from the oligarchy. The Librem 5 v2 puts you in control of your data, combining that with the ease of use we expect in the modern era". Its specifications include a 5.7-inch 720 x 1440 display, hardware kill switches, and a removable 4500mAh battery, writes Slashdot reader BrianFagioli: The asking price is $1,599, with production delivery targeted for roughly May 2028.. Purism acknowledges remaining work on graphics, peripheral drivers, ARM64 app emulation, and power management. NERDS.xyz argues that the concept is appealing, but the price and wait are difficult to justify for an everyday phone. Android already uses the Linux kernel, so the appeal here is an alternative built around PureOS and the broader desktop Linux ecosystem. Is this a reasonable cost to help fund that alternative, or too much money for hardware and software that buyers cannot yet evaluate as a finished product? Purism says they've already received 53 of their goal of 2,500 orders (2%) with 91 days still remaining. (The campaign runs through February 15 of 2027)

Read more of this story at Slashdot.

16 Nov 2026 8:34am GMT

ULA Vulcan Rocket Failure Destroys 40 Amazon Leo Satellites

United Launch Alliance's new heavy-lift Vulcan rocket "malfunctioned while climbing into space yesterday," writes Engadget, "destroying its payload of 40 Amazon Leo internet satellites..." Launch failures are always a risk, but amazingly, United Launch Alliance had never experienced one previously. Since the company formed in 2006 as a partnership between Boeing and Lockheed Martin, its Atlas V rocket has been famously dependable. Now, the company's more powerful, more complex Vulcan will be under review by engineers and is facing a possible grounding... As well as being a major setback for United Launch Alliance, the failed launch will be a blow to Amazon's Leo internet satellite system, intended to rival SpaceXSI's Starlink network. Leo has 38 Vulcan flights booked to launch its satellites, following eight successful Atlas V missions. Many of those are now likely to be delayed. Amazon's other launch provider, Jeff Bezos' Blue Origin, suffered its own setback in May when its New Glenn rocket exploded on the launchpad. The Federal Communications Commission required Amazon Leo to have 1,600 satellites in orbit by July 31, 2026, but so far it only has around 390 in service... "No operator could have predicted that all three core heavy-lift launch programs... would experience repeated, concurrent scheduling slips severe enough to exhaust the buffers Amazon Leo had built in," the company said back in July. "Every flight generates data, and every flight teaches us something," the company said in a post on X, promising a transparent and thorough investigation. "We will provide further updates when new information becomes available. Thanks to long-time Slashdot reader schwit1 for sharing the news.

Read more of this story at Slashdot.

16 Nov 2026 6:34am GMT

AI-Generated Books Confront Publishing Industry With Big Questions

Romance novelist Coral Hart publishes her own romance novels for the Kindle, and found a kind of superpowere when she realized "the algorithm favours those who can produce a new book at least once a month," reports The Guardian: Hart says she knows of authors who hire more than a dozen ghostwriters to keep pace. By herself, Hart can write 10,000 words a day, but AI could help her produce many more. Since 2025 she has written 370 novels under 21 pen names using AI, earning herself "high six figures". Like any Kindle Unlimited author, she is only paid per pages read: it would make no business sense for her to churn out books that readers quickly abandon... "So, it's not taking the human out of the equation. It's taking the friction and the time and the business blocks out of the way." One study (awaiting peer review), led by Tuhin Chakrabarty of Stony Brook University, estimates that around one fifth of recently self-published books contain at least 25% AI-generated text. Hart now teaches courses on how to use AI to produce books. Unless disclosing the use of AI becomes a legal requirement, she advises other authors not to do so because of the public response. "The minute someone discloses [AI use] they get death threats, they get called names, they're ousted," she says.... In the literary world, many people fear the tech will undercut and replace them. "I think people are very afraid of AI, and people in publishing are delusional in thinking that it's not going to overtake our industry, that their screaming on social media is going to stop it." But the anger comes from another place, too. If large language models can spit out books that people want to read, or produce a convincing pastiche of your favourite writer, that's almost certainly because they were trained on established writers' stolen work.... Many writers oppose AI for both moral and aesthetic reasons. One group of 70 prominent authors wrote an open letter calling on the big five publishers - Penguin Random House, Hachette, HarperCollins, Simon & Schuster and Macmillan - to promise that they will "never release books that were created by a machine". The publishers did not promise. [Tess Callero, a literary agent with Europa Content, says] "...you have to wonder the reason they aren't. Is it because they see a future in which potentially these books could be monetised?"] So where do we go from here? Will big name writers win the argument for keeping AI out of literature, or will our bookshelves and e-readers soon be crammed full of AI-generated stories? And if a reader can't distinguish human from machine writing, does it still matter? The Guardian's author notes this new technology brings new challenges to the book publishing world: Publishers have concerns about US copyright law, "which specifies that a book must be 'human authored' and considers AI-generated text public domain. " The article notes high-profile books being canceled after accusations their writers used AI. But even in those cases, "Another unresolved question is if and when publishers should withdraw books," since if publishers liked it enough to make the deal, shouldn't they stand behind that judgment? And should there be a way for authors who want to experiment with AI to work with top book publishers? (One theory is publishing houses are afraid of alienating a handful of top writers who almost universally oppose AI.) "Right now, to write without the aid of a machine is to swim against a strong cultural tide," concludes the article's author, noting a recurring reaction from friends who "have looked at me with something close to pity when I tell them I would never use AI to write."

Read more of this story at Slashdot.

16 Nov 2026 3:45am GMT

15 Nov 2026

feedOSnews

KDE will now load XWayland on demand

When running KDE, the X11 compatibility layer for Wayland, XWayland, always runs, even if there isn't anything on the system still requiring the legacy X server to work. In the next step towards a Wayland-only world, the KDE people have reached a major milestone: XWayland now only runs when actually needed. This week a significant technical milestone was achieved: the XWayland compatibility layer is now loaded only when needed. Previously it had always been running even when no apps were using it, and fixing this required porting various system services away from legacy X11 code paths. This work was done by Vlad Zahorodnii, David Edmundson, and David Redondo, and will ship in Plasma 6.9. ↫ Nate Graham This frees up some system resources, which is always a welcome improvement. I do wonder how this might impact the load times of legacy X applications, but I have a feeling it's close to immeasurable.

15 Nov 2026 11:41pm GMT

Redox gets Go, GIMP, and more

I love and admire the Redox project, but their insistence on fudging the publication dates of their monthly progress reports really bothers me, for some reason. No, I'm not 16 days late - the report covering October was published only yesterday evening, and not on 31 October as the website claims. None of this matters to anyone but weird people such as myself, but I still want to get it off my chest. Don't bother any Redox people about this. Anyway, the big news for the month of October is the port of the official Go programming language compiler, allowing for cross-compilation and self-hosted compilation using relibc. Another major port also made its way to Redox in October: GIMP now runs on Redox, using the Orbital backend of the GTK port. The work to make Redox compatible with Cloud Hypervisor is also complete, with more information in its own dedicated article. Video playback in WebKitGTK3 has been fixed as well, and even YouTube works now which is quite neat. There's a ton more in this report, like an updated Servo port, NUMA support has been tested on real hardware for the first time and seems to work, work on rootless package installation has begun, and much more.

15 Nov 2026 11:31pm GMT

Disk encryption on NetBSD: achieving secrecy

NetBSD developer Nia Alarie has written a guide on how to set up a NetBSD system with disk encryption that's quite useful for those of us who deeply care about such a level of security. On top of that, the guide is also interesting if you just want to learn a bit more about how NetBSD works. The guide is written for sparc64, but should work on more mainstream architectures just as well. A guide written by a NetBSD developer is obviously going to employ some exotic or weird hardware. As is tradition.

15 Nov 2026 11:21pm 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