Feed aggregator

Linux gaming is finally great, and these 4 distros are leading the way  MakeUseOf

Elementary OS 8.1 arrives with Linux 6.14 kernel and smoother multitasking  Neowin

Uber and Lyft plan to trial robotaxis in London starting in 2026 using autonomous vehicles from Baidu, as the UK fast-tracks approvals for self-driving cars on public roads. CNBC reports: Lyft's testing of Baidu's initial fleet of dozens of vehicles will begin in 2026, pending regulatory approval, "with plans to scale to hundreds from there," Lyft CEO David Risher said in a post on social media platform X on Monday. Meanwhile, Uber said that its first pilot is expected to start in the first half of 2026. "We're excited to accelerate Britain's leadership in the future of mobility, bringing another safe and reliable travel option to Londoners next year," the company added. The moves add to Baidu's growing global footprint, which it says includes 22 cities and more than 250,000 weekly trips, as it races against other Chinese players like WeRide and Western giants like Alphabet's Waymo. The UK, in particular, has seen a wave of interest from driverless taxi companies, following the government's announcement in June that it would accelerate its plans to allow autonomous vehicle tech on public roads. The government now aims to begin permitting robotaxis to operate in small-scale pilots starting in spring 2026, with Baidu likely aiming to be among the first. The city of London has also established a "Vision Zero" goal to eliminate all serious injuries and deaths in its transportation systems by 2041, with autonomous driving technology expected to play a large role.

Read more of this story at Slashdot.

Red Hat Enterprise Linux Revenue Statistics  commandlinux.com

Here's our 2025 GOTY picks  GamingOnLinux

Meta Is Using The Linux Scheduler Designed For Valve's Steam Deck On Its Servers  Phoronix

joshuark shares a report from Ars Technica: For the better part of two months last year, most of us had no idea how serious the problems were with Boeing's Starliner spacecraft docked at the International Space Station. A safety advisory panel found this uncertainty also filtered through NASA's workforce. [...] The Starliner capsule was beset by problems with its maneuvering thrusters and pernicious helium leaks on its 27-hour trip from the launch pad to the ISS. For a short time, Starliner commander Wilmore lost his ability to control the movements of his spacecraft as it moved in for docking at the station in June 2024. Engineers determined that some of the thrusters were overheating and eventually recovered most of their function, allowing Starliner to dock with the ISS. [...] Throughout that summer, managers from NASA and Boeing repeatedly stated that the spacecraft was safe to bring Wilmore and Williams home if the station needed to be evacuated in an emergency. But officials on the ground ordered extensive testing to understand the root of the problems. Buried behind the headlines, there was a real chance NASA managers would decide -- as they ultimately did -- not to put astronauts on Boeing's crew capsule when it was time to depart the ISS. [...] It would have been better, [Charlie Precourt, a former space shuttle commander and now a member of NASA's Aerospace Safety Advisory Panel (ASAP)] and other panel members said Friday, if NASA made a formal declaration of an in-flight "mishap" or "high visibility close call" soon after the Starliner spacecraft's troubled rendezvous with the ISS. Such a declaration would have elevated responsibility for the investigation to NASA's safety office. [...] After months of testing and analysis, NASA officials were unsure if the thruster problems would recur on Starliner's flight home. They decided in August 2024 to return the spacecraft to the ground without the astronauts, and the capsule safely landed in New Mexico the following month. The next Starliner flight will carry only cargo to the ISS. The safety panel recommended that NASA review its criteria and processes to ensure the language is "unambiguous" in requiring the agency to declare an in-flight mishap or a high-visibility close call for any event involving NASA personnel "that leads to an impact on crew or spacecraft safety."

Read more of this story at Slashdot.

Using An E-Book Reader As A Secondary Display  Hackaday

Lubuntu vs. Xubuntu: Which Ubuntu flavor is right for you - my expert advice  ZDNET

Linux 6.19 boosts old AMD GCN HD 7900 GPU performance by ~30% with AMDGPU  VideoCardz.com

Stop Manually Checking GitHub Releases — These Tools Automatically Install & Update Apps on Linux  It's FOSS

Tony Isaac shares a report from NPR: The U.S. government calculates the country's official time using more than a dozen atomic clocks at a federal facility northwest of Denver. But when a destructive windstorm knocked out power to the National Institute of Standards and Technology (NIST) laboratory in Boulder on Wednesday and a backup generator subsequently failed, time ever so slightly slowed down. The lapse "resulted in NIST UTC [universal coordinated time] being 4.8 microseconds slower than it should have been," NIST spokesperson Rebecca Jacobson said in an email. [...] Since 2007, the official time of the U.S. has been determined by the commerce secretary, who oversees NIST, along with the U.S. Navy. The national time standard is known as NIST UTC. (Somewhat confusingly, UTC itself is a separate, global time standard to which the U.S. and other countries contribute measurements.) NIST currently calculates the standard using a weighted average of the readings of 16 atomic clocks situated across the Boulder campus. Atomic clocks, including hydrogen masers and cesium beam clocks, rely on the natural resonant frequencies of atoms to tell time with extremely high accuracy. All of the atomic clocks continued ticking through the power outage last week thanks to their battery backup systems, according to NIST supervisory research physicist Jeff Sherman. What failed was the connection between some of the clocks and NIST's measurement and distribution systems, he said. Some critical operations staff who were still on site following the severe weather were able to restore backup power by activating a diesel generator the team had kept in reserve, Sherman said.

Read more of this story at Slashdot.

jdSystemMonitor: More Than Your Regular System Monitor on Linux  It's FOSS

Linux Mint 22.3 Beta Released, This is What’s New  OMG! Ubuntu

"Garmin's Collier Trophy award-winning Autonomi emergency Autoland, a system designed to safely land an aircraft in the event of pilot incapacitation, made its first real-world use and save on Saturday," writes Slashdot reader slipped_bit. AvBrief.com reports: Social media posts from flight tracking hobbyists reported a King Air 200 squawked 7700 about 2 p.m. local time today. The Autoland system was initiated and landed the aircraft at Rocky Mountain Metropolitan Airport near Denver. A recording from LiveATC's feed of the airport's tower frequency includes a robotic female voice declaring a pilot incapacitation and the intention to land on Runway 30. The aircraft landed successfully and there have been no reports of injuries. The nature of the incapacitation and the condition of the pilot have not been released. VASAviation put together this nice animation of the event [here]. The aircraft, N479BR, was being operated by Buffalo River Outfitters from Aspen to Rocky Mountain Metropolitan. It's not clear how many people were on board. The system appeared to work flawlessly, and the controller at Rocky Mountain Metropolitan seemed to take it in stride, accommodating as many requests as he could before shutting down the airport for the landing.

Read more of this story at Slashdot.

The FCC has banned approval of new foreign-made drones and components, citing "an unacceptable risk" to national security. The move will most heavily impact DJI but it "does not affect drones or drone components that are currently sold in the United States." Reuters reports: The tech was placed on the commission's "Covered List," barring DJI and other foreign drone manufacturers from receiving the FCC's approval to sell new drone models for import or sale in the U.S. In Monday's announcement, the agency said that the move "will reduce the risk of direct [drone] attacks and disruptions, unauthorized surveillance, sensitive data exfiltration and other [drone] threats to the homeland." FCC Chair Brendan Carr said in a statement that while drones offer the potential to boost public safety and the U.S.' posture on global innovation, "criminals, terrorists and hostile foreign actors have intensified their weaponization of these technologies, creating new and serious threats to our homeland." The ruling comes as China hawks in Congress amplify warnings about the security risks of drones made by DJI, which accounts for more than 90% of the global market share. But efforts to crack down on Capitol Hill have been met with some pushback due to the potential impacts of curbing the drone usage on U.S. businesses and law enforcement. A wide variety of sectors, including construction, energy, agriculture and mining companies, as well as local police and fire departments across the country, deploy DJI-made drones.

Read more of this story at Slashdot.

Intel Linux Driver Preps For Up To 13 Different Panther Lake H SoCs  Phoronix

Microsoft plans to eliminate all C and C++ code across its major codebases by 2030, replacing it with Rust using AI-assisted, large-scale refactoring. "My goal is to eliminate every line of C and C++ from Microsoft by 2030," Microsoft Distinguished Engineer Galen Hunt writes in a post on LinkedIn. "Our strategy is to combine AI and Algorithms to rewrite Microsoft's largest codebases. Our North Star is '1 engineer, 1 month, 1 million lines of code.' To accomplish this previously unimaginable task, we've built a powerful code processing infrastructure. Our algorithmic infrastructure creates a scalable graph over source code at scale. Our AI processing infrastructure then enables us to apply AI agents, guided by algorithms, to make code modifications at scale. The core of this infrastructure is already operating at scale on problems such as code understanding." Hunt says he's looking to hire a Principal Software Engineer to help with this effort. "The purpose of this Principal Software Engineer role is to help us evolve and augment our infrastructure to enable translating Microsoft's largest C and C++ systems to Rust," writes Hunt. "A critical requirement for this role is experience building production quality systems-level code in Rust -- preferably at least 3 years of experience writing systems-level code in Rust. Compiler, database, or OS implementation experience is highly desired. While compiler implementation experience is not required to apply, the willingness to acquire that experience in our team is required."

Read more of this story at Slashdot.

Alphabet is acquiring Intersect for $4.75 billion to accelerate data center and power-generation capacity as AI infrastructure demand surges. CNBC reports: Alphabet said Intersect's operations will remain independent, but that the acquisition will help bring more data center and generation capacity online faster. "Intersect will help us expand capacity, operate more nimbly in building new power generation in lockstep with new data center load, and reimagine energy solutions to drive U.S. innovation and leadership," Sundar Pichai, CEO of Google and Alphabet, said in a statement. Google already had a minority stake in Intersect from a funding round that was announced last December. In a release at the time, Intersect said its strategic partnership with Google and TPG Rise Climate aimed to develop gigawatts of data center capacity across the U.S., including a $20 billion investment in renewable power infrastructure by the end of the decade. Alphabet said Monday that Intersect will work closely with Google's technical infrastructure team, including on the companies' co-located power site and data center in Haskell County, Texas. Google previously announced a $40 billion investment in Texas through 2027, which includes new data center campuses in the state's Haskell and Armstrong counties.

Read more of this story at Slashdot.

An anonymous reader quotes a report from the Associated Press: With just three days to go before Christmas, a cyberattack knocked France's national postal service offline Monday, blocking and delaying package deliveries and online payments. The timing was miserable for millions of people at the height of the Christmas season, as frazzled postal workers fended off frustrated customers. No one immediately claimed responsibility, but suspicions abounded. What the postal service La Poste called a ''major network incident'' remained unresolved by Monday evening, more than eight hours after it was first reported. For a company that delivered 2.6 billion packages last year and employs more than 200,000 people, that's a big hit. La Poste said in a statement that a distributed denial of service incident, or DDoS, "rendered its online services inaccessible." It said the incident had no impact on customer data, but disrupted package delivery. Letters, including holiday greeting cards, could still be mailed and delivered. But transactions requiring tracking or access to the postal service internal computer systems were impossible. The cyberattack also hurt online banking. Customers of the company's banking arm, La Banque Postale, were blocked from using the application to approve payments or conduct other banking services. The bank redirected approvals to text messages instead. "Our teams are mobilized to resolve the situation quickly," the bank said in messages posted on social networks. The disruption came a week after France's government was targeted by a cyberattack that targeted the Interior Ministry, in charge of national security.

Read more of this story at Slashdot.