An anonymous reader quotes a report from Ars Technica: When the COVID-19 pandemic forced kids to stay home, educators flocked to VMware, and thousands of school districts adopted virtualization. The technology became a solution for distance learning during the pandemic and after, when events such as bad weather and illness can prevent children from physically attending school. However, the VMware being sold to K-12 schools today differs from the VMware that existed before and during the pandemic. Now a Broadcom business, the platform features higher prices and a business strategy that favors big spenders. This has created unique problems for educational IT departments juggling restrictive budgets and multiple technology vendors with children's needs.

Ars Technica recently spoke with an IT director at a public school district in Indiana. The director requested anonymity for themself and the district out of concern about potential blowback. The director confirmed that the district has five schools and about 3,000 students. The district started using VMware's vSAN, a software-defined storage offering, and the vSphere virtualization platform in 2019. The Indiana school system bought the VMware offerings through a package that combined them with VxRail, which is hyperconverged infrastructure (HCI) hardware that Dell jointly engineered with VMware.

However, like many of VMware customers, the Indiana school district was priced out of VMware after Broadcom's acquisition of the company. The IT director said the district received a quote that was "three to six" times higher than expected. This came as the school district is looking to manage changes in education-related taxes and funding over the next few years. As a result, the district's migration from VMware is taking IT resources from other projects, including ones aimed at improving curriculum. For instance, the Indiana district has been trying to bolster its technology curriculum, the IT director said. One way is through a summer employment program for upperclassmen that teaches how to use real-world IT products, like VMware and Cisco Meraki technologies. The district previously relied on VMware-based virtual machines (VMs) for creating "very easily and accessible" test environments for these students. But the school is no longer able to provide that opportunity, creating a learning "barrier," as the IT director put it. The IT director told Ars that dealing with a migration could be "catastrophic in that that's too much work for one person," adding: "It could be a chokehold, essentially, to where they're going to be basically forced into switching platforms -- maybe before they were anticipating -- or paying exorbitant prices that have skyrocketed for absolutely no reason. Nothing on the software side has changed. It's the same software. There's no features being added. Nobody's benefiting from the higher prices on the education side."

By 2028, Gartner research VP Julia Palmer predicts that VMware will lose 35% of its current workloads as Broadcom's licensing changes and rising costs push customers toward competitors like Nutanix and public clouds. The Register reports: On Wednesday at the analyst firm's Symposium event in Australia, Palmer pointed out that the Broadcom business unit recently tweaked its licensing program so that hyperscalers can no longer sell VMware subscriptions to users of their hosted VMware services. Customers must instead buy direct from Broadcom and use license portability entitlements for any VMware infrastructure they host in hyperscale clouds. Palmer said that decision shows VMware does not consider hyperscalers strategic partners, and she thinks the feeling is mutual. Hyperscalers nevertheless welcome customers who use them to run VMware workloads "because they know over time they will convert you to 'proper cloud'."

Which is one reason she expects VMware will lose so many workloads: Hyperscalers will use their engagements with VMware customers to extol the virtue of public clouds. Palmer thinks VMware customers should heed that pitch. "We are all addicted to hypervisors, and that needs to change," Palmer said, not least because Broadcom's acquisition of VMware shows how lock-in to a virtualization platform can be costly. But she counseled against planning to move all workloads off VMware, as no rival vendor offers a superior platform and a full migration will take three or more years. Palmer instead advised assessing which applications are ripe for modernization and re-platforming, and shifting those -- a job that can take up to a year.

Tesco is suing Broadcom and reseller Computacenter for at least $134 million, claiming that VMware's perpetual license support agreements were breached after Broadcom's acquisition. The supermarket giant warned it "may not be able to put food on the shelves if the situation goes pear-shaped," writes The Register's Simon Sharwood. From the report: Court documents seen by The Register assert that in January 2021 Tesco acquired perpetual licenses for VMware's vSphere Foundation and Cloud Foundation products, plus subscriptions to Virtzilla's Tanzu products, and agreed a contract for support services and software upgrades that run until 2026. Tesco claims VMware also agreed to give it an option to extend support services for an additional four years. All of this happened before Broadcom acquired VMware and stopped selling support services for software sold under perpetual licenses. Broadcom does sell support to those who sign for its new software subscriptions.

The supermarket giant says Broadcom's subscriptions mean it must pay "excessive and inflated prices for virtualization software for which Tesco has already paid," and "is unable any longer to purchase stand-alone Virtualization Support Services for its Perpetually Licensed Software without also having to purchase duplicative subscription-based licenses for those same Software products which it already owns." The complaint also alleges that Tesco's contracts with VMware include eligibility for software upgrades, but that Broadcom won't let the retailer update its perpetual licenses to cover the new Cloud Foundation 9.

The filing names Computacenter as a co-defendant as it was the reseller that Tesco relied on for software licenses, and the retailer feels it's breached contracts to supply software at a fixed price. Tesco's filing also mentions Broadcom's patch publication policy, which means users who don't acquire subscriptions can't receive all security updates and don't receive other fixes. The retailer thinks its contracts mean it is entitled to those updates. The filing suggests that lack of support is not just a legal matter, but may have wider implications because VMware software, and support for it "are essential for the operations and resilience of Tesco's business and its ability to supply groceries to consumers across the UK and Republic of Ireland."

"VMware Virtualization Software underpins the servers and data systems that enable Tesco's stores and operations to function, hosting approximately 40,000 server workloads and connecting to, by way of illustration, tills in Tesco stores," the filing states. Tesco's filing warns that Broadcom, VMware, and Computacenter are each liable for at least $134 million damages, plus interest, and that the longer the dispute persists the higher damages will climb.

Protected KVM (pKVM), the hypervisor powering the Android Virtualization Framework, has officially achieved SESIP Level 5 certification (in testing by cybersecurity lab Dekra against the TrustCB SESIP scheme).

Google's security blog called the certification "a watershed moment," and a "new benchmark" for both open-source security — and for the future of consumer electronics. "It provides a single, open-source, and exceptionally high-quality firmware base that all device manufacturers can build upon." This makes pKVM the first software security system designed for large-scale deployment in consumer electronics to meet this assurance bar. The implications for the future of secure mobile technology are profound. With this level of security assurance, Android is now positioned to securely support the next generation of high-criticality isolated workloads. This includes vital features, such as on-device AI workloads that can operate on ultra-personalized data, with the highest assurances of privacy and integrity...

Achieving Security Evaluation Standard for IoT Platforms (SESIP) Level 5 is a landmark because it incorporates AVA_VAN.5, the highest level of vulnerability analysis and penetration testing under the ISO 15408 (Common Criteria) standard. A system certified to this level has been evaluated to be resistant to highly skilled, knowledgeable, well-motivated, and well-funded attackers who may have insider knowledge and access. This certification is the cornerstone of the next-generation of Android's multi-layered security strategy. Many of the TEEs (Trusted Execution Environments) used in the industry have not been formally certified or have only achieved lower levels of security assurance... Looking ahead, Android device manufacturers will be required to use isolation technology that meets this same level of security for various security operations that the device relies on. Protected KVM ensures that every user can benefit from a consistent, transparent, and verifiably secure foundation.
"This achievement represents just one important aspect of the immense, multi-year dedication from the Linux and KVM developer communities and multiple engineering teams at Google developing pKVM and AVF," the post concludes.

"We look forward to seeing the open-source community and Android ecosystem continue to build on this foundation, delivering a new era of high-assurance mobile technology for users."

ZDNet's Steven Vaughan-Nichols shares his list of "what's new and improved" in the latest Linux 6.16 kernel. An anonymous reader shares an excerpt from the report: First, the Rust language is continuing to become more well-integrated into the kernel. At the top of my list is that the kernel now boasts Rust bindings for the driver core and PCI device subsystem. This approach will make it easier to add new Rust-based hardware drivers to Linux. Additionally, new Rust abstractions have been integrated into the Direct Rendering Manager (DRM), particularly for ioctl handling, file/GEM memory management, and driver/device infrastructure for major GPU vendors, such as AMD, Nvidia, and Intel. These changes should reduce vulnerabilities and optimize graphics performance. This will make gamers and AI/ML developers happier.

Linux 6.16 also brings general improvements to Rust crate support. Crate is Rust's packaging format. This will make it easier to build, maintain, and integrate Rust kernel modules into the kernel. For those of you who still love C, don't worry. The vast majority of kernel code remains in C, and Rust is unlikely to replace C soon. In a decade, we may be telling another story. Beyond Rust, this latest release also comes with several major file system improvements. For starters, the XFS filesystem now supports large atomic writes. This capability means that large multi-block write operations are 'atomic,' meaning all blocks are updated or none. This enhances data integrity and prevents data write errors. This move is significant for companies that use XFS for databases and large-scale storage.

Perhaps the most popular Linux file system, Ext4, is also getting many improvements. These boosts include faster commit paths, large folio support, and atomic multi-fsblock writes for bigalloc filesystems. What these improvements mean, if you're not a file-system nerd, is that we should see speedups of up to 37% for sequential I/O workloads. If your Linux laptop doubles as a music player, another nice new feature is that you can now stream your audio over USB even while the rest of your system is asleep. That capability's been available in Android for a while, but now it's part of mainline Linux.

If security is a top priority for you, the 6.16 kernel now supports Intel Trusted Execution Technology (TXT) and Intel Trusted Domain Extensions (TDX). This addition, along with Linux's improved support for AMD Secure Encrypted Virtualization and Secure Memory Encryption (SEV-SNP), enables you to encrypt your software's memory in what's known as confidential computing. This feature improves cloud security by encrypting a user's virtual machine memory, meaning someone who cracks a cloud can't access your data. Linux 6.16 also delivers several chip-related upgrades. It introduces support for Intel's Advanced Performance Extensions (APX), doubling x86 general-purpose registers from 16 to 32 and boosting performance on next-gen CPUs like Lunar Lake and Granite Rapids Xeon. Additionally, the new CONFIG_X86_NATIVE_CPU option allows users to build processor-optimized kernels for greater efficiency.

Support for Nvidia's AI-focused Blackwell GPUs has also been improved, and updates to TCP/IP with DMABUF help offload networking tasks to GPUs and accelerators. While these changes may go unnoticed by everyday users, high-performance systems will see gains and OpenVPN users may finally experience speeds that challenge WireGuard.

VMware is overhauling its partner program again under Broadcom's direction, drastically reducing the number of authorized partners -- especially small and mid-size ones -- while ending the white label program by October 31, 2025. The Register reports: Australian IT service provider Interactive outlined the changes on Wednesday in a post that explained the changes with the following five points:

- Partner Reduction: The new program significantly reduces the number of authorized partners, being a by-invitation-only program. As a result on July 15, 2025 VCSP partners who are not invited to participate in the new Program for VCSP partners will be sent a notice of non-renewal.
- Transition Period Until 31 October, 2025: Non-invited partners can continue to transact until 31 October 2025. After that date, they may only service existing VCSP commitment contracts for the remainder of the current term. No new commitment contracts or renewals will be accepted for those partners.
- White Label Program Ending: Broadcom is also sunsetting the White Label model on 31 October 2025. The same transitional commercial conditions apply to White Label contracts as stated above.
- Immediate Impact: Departing partners are encouraged to work with authorized VCSP partners to ensure a smooth transition for customers who seek to renew a service at the end of their current term.
- Shift Toward Hyperscale Private Compute: Broadcom is reshaping its vision for private compute, whereby VMware Cloud Foundation 9 underpins a small number [of] hyperscale private cloud platforms in each region. A future where customers buy managed infrastructure from partners like Interactive to support their compute requirements.

Interactive also warned that customers whose partners are no longer part of the partner program could expect the change to effect:

- Your ability to renew licenses through your existing partner
- The support and service quality you've come to expect
- Potential delays or confusion during upcoming renewals or service requests
- Potential cost increases as partner consolidation may led additional costs for migration and re-onboarding, and reduced bundling options that previously allowed for greater cost efficiencies VMware also told The Register that "Non-renewing partners can continue to support their existing customers until the end of their current commit contract term including co-termed capacity orders. Non-renewing partners are encouraged to work with authorized VCSP partners to ensure a smooth transition for customers who seek to renew a service at the end of their current term."

Making matters worse: VMware on Tuesday divulged three critical flaws in eights of its products rated 9.3/10.

Apple's macOS 26 "Tahoe" introduces a new disk image format called ASIF, designed to dramatically improve performance over previous formats like UDRW and sparse bundles -- achieving near-native read/write speeds for virtual machines and general disk image use. The Eclectic Light Company reports: Apple provides few technical details, other than stating that the intrinsic structure of ASIF disk images doesn't depend on the host file system's capabilities, and their size on the host depends on the size of the data stored in the disk. In other words, they're a sparse file in APFS, and are flagged as such. [...]

Conclusions:
- Where possible, in macOS 26 Tahoe in particular, VMs should use ASIF disk images rather than RAW/UDRW.
- Unless a sparse bundle is required (for example when it's hosted on a different file system such as that in a NAS), ASIF should be first choice for general purpose disk images in Tahoe.
- It would be preferable for virtualizers to be able to call a proper API rather than a command tool.
- Keep an eye on C-Command's DropDMG. I'm sure it will support ASIF disk images soon.

An anonymous reader shares a blog post from Google: Today, we're bringing you Android 16, rolling out first to supported Pixel devices with more phone brands to come later this year. This is the earliest Android has launched a major release in the last few years, which ensures you get the latest updates as soon as possible on your devices. Android 16 lays the foundation for our new Material 3 Expressive design, with features that make Android more accessible and easy to use.

An anonymous reader quotes a report from The Register: Broadcom's VMware business unit has dropped the lowest tier of its channel program, a move one analyst told The Register will benefit its rivals. The virtualization pioneer currently operates a four-tier channel program spanning Pinnacle, Premier, Select, and Registered partners. On Sunday the business unit announced the retirement of the Registered tier. A blog post written by Brian Moats, Broadcom's Senior Vice President for Global Commercial Sales and Partners, states VMware made the decision because "the vast majority of customer impact and business momentum comes from partners operating within the top three tiers."

Laura Falko, Broadcom's Head of Global Partner Programs, Marketing & Experience, told The Register "The vast majority of these [Registered] partners are inactive and lack the capabilities to support customers through VMware's evolving private cloud journey. That's why the Registered tier is being retired to ensure every active partner meets a higher standard of technical, sales, and service readiness." Falko told us VMware will give Registered partners 60 days' notice before deauthorization and then "work proactively with affected customers to transition them to qualified partners in the new ecosystem, ensuring continuity and support throughout the change."

VMware has also introduced new requirements for partners in its remaining tiers. The virtualization giant will require Pinnacle and Premier partners to maintain dedicated sales and technical resources, and to "execute joint business plans with VMware to ensure alignment and delivery with mutual results." The Broadcom business unit is also "beginning the process of transitioning partners who no longer meet the minimum program requirements or have not demonstrated consistent engagement," suggesting even Pinnacle, Premier, and Select partners are not safe. The Register asked VMware to define "consistent engagement" and Falko told us it includes "regular deal activity," ongoing participation in joint sales activities, staying up to date with training, and "sustained, proactive commitment to a partner's VMware customer base." The changes will only apply in its Americas, and Asia-Pacific and Japan regions. Broadcom didn't explain why Europe was excluded.

The Register notes that trade associations in Europe have criticized Broadcom's changes at VMware and urged the European Commission to investigate the company.

Longtime Slashdot reader me34point5 writes: OpenBSD quietly released the new version (7.7) of its "secure by default" operating system. This is the 58th release. Changes include improved hardware and VMM support, along with many kernel improvements. This release brings several specific improvements, including performance boosts on ARM64, Arm SVE support, AMD SEV virtualization enhancements, better low-memory handling on i386, and improved suspend/hibernate and SMP performance. It also updates graphics drivers with support for AMD Ryzen IA 300, Radeon RX 9070, and Intel Arrow Lake, along with expanded hardware support for MediaTek SoCs.

A full list of changes can be found here.

AMD has open-sourced its "GPU-IOV Module" for enabling SR-IOV-based virtualization on Instinct accelerators using the Linux kernel and KVM hypervisor, with features like GPU scheduling and VF/PF management. Notably, AMD plans to extend this virtualization support to client Radeon GPUs. Phoronix reports: The AMD GPU-IOV Module is for the Linux kernel and for providing SR-IOV based hardware virtualization in conjunction with the KVM hypervisor. GIM provides the GPU IOV virtualization, virtual function (VF) configuration and enablement, GPU scheduling for world switch, hang detection and FLR reset, and PF/VF handshake capabilities. Initially the AMD GIM driver is for the Instinct MI300X hardware and tested atop Ubuntu 22.04 LTS with ROCm 6.4. Those interested can find the AMD GIM code currently via GitHub. It's not laid out in the repository or any other public communications I've seen what any upstreaming plans are for this GIM driver to get it into the mainline Linux kernel.

An anonymous reader quotes a report from Android Authority: No matter the manufacturer, every Android phone has one thing in common: its software base. Manufacturers can heavily customize the look and feel of the Android OS they ship on their Android devices, but under the hood, the core system functionality is derived from the same open-source foundation: the Android Open Source Project. After over 16 years, Google is making big changes to how it develops the open source version of Android in an effort to streamline its development. [...] Beginning next week, all Android development will occur within Google's internal branches, and the source code for changes will only be released when Google publishes a new branch containing those changes. As this is already the practice for most Android component changes, Google is simply consolidating its development efforts into a single branch.

This change will have minimal impact on regular users. While it streamlines Android OS development for Google, potentially affecting the speed of new version development and bug reduction, the overall effect will likely be imperceptible. Therefore, don't expect this change to accelerate OS updates for your phone. This change will also have minimal impact on most developers. App developers are unaffected, as it pertains only to platform development. Platform developers, including those who build custom ROMs, will largely also see little change, since they typically base their work on specific tags or release branches, not the main AOSP branch. Similarly, companies that release forked AOSP products rarely use the main AOSP branch due to its inherent instability.

External developers who enjoy reading or contributing to AOSP will likely be dismayed by this news, as it reduces their insight into Google's development efforts. Without a GMS license, contributing to Android OS development becomes more challenging, as the available code will consistently lag behind by weeks or months. This news will also make it more challenging for some developers to keep up with new Android platform changes, as they'll no longer be able to track changes in AOSP. For reporters, this change means less access to potentially revealing information, as AOSP patches often provide insights into Google's development plans. [...] Google will share more details about this change when it announces it later this week. If you're interested in learning more, be sure to keep an eye out for the announcement and new documentation on source.android.com. Android Authority's Mishaal Rahman says Google is "committed to publishing Android's source code, so this change doesn't mean that Android is becoming closed-source."

"What will change is the frequency of public source code releases for specific Android components," says Rahman. "Some components like the build system, update engine, Bluetooth stack, Virtualization framework, and SELinux configuration are currently AOSP-first, meaning they're developed fully in public. Most Android components like the core OS framework are primarily developed internally, although some features, such as the unlocked-only storage area API, are still developed within AOSP."

Google has introduced a Debian Linux terminal app for Android in its ongoing effort to transform Android into a versatile desktop OS. It's initially available on Pixel devices running Android 15 but will be expanded to "all sufficiently robust Android phones" when Android 16 arrives later this year," writes ZDNet's Steven Vaughan-Nichols. An anonymous reader shares an excerpt from the report: Today, Linux is only available on the latest Pixel devices running Android 15. When Android 16 arrives later this year, it's expected that all sufficiently robust Android phones will be able to run Linux. Besides a Linux terminal, beta tests have already shown that you should be able to run desktop Linux programs from your phone -- games like Doom, for example. The Linux Terminal runs on top of a Debian Linux virtual machine. This enables you to access a shell interface directly on your Android device. And that just scratches the surface of Google's Linux Terminal. It's actually a do-it-all app that enables you to download, configure, and run Debian. Underneath Terminal runs the Android Virtualization Framework (AVF). These are the APIs that enable Android devices to run other operating systems.

To try the Linux Terminal app, you must activate Developer Mode by navigating to Settings - About Phone and tapping the build number seven times. I guess Google wants to make sure you want to do this. Once Developer Mode is enabled, the app can be activated via Settings - System - Developer options - Linux development environment. The initial setup may take a while because it needs to download Debian. Typically this is a 500MB download. Once in place, it allows you to adjust disk space allocation, set port controls for network communication, and recover the virtual machine's storage partition. However, it currently lacks support for graphical user interface (GUI) applications. For that, we'll need to wait for Android 16.

According to Android specialist Mishaal Rahman, 'Google wants to turn Android into a proper desktop operating system, and in order to do that, it has to make it work better with traditional PC input methods and display options. Therefore, Google is now testing new external display management tools in Android 16 that bring Android closer to other desktop OSes.'

Slashdot reader headlessbrick writes: Google security researchers have discovered a way to bypass AMD's security, enabling them to load unofficial microcode into its processors and modify the silicon's behaviour at will. To demonstrate this, they created a microcode patch that forces the chips to always return 4 when asked for a random number.

Beyond simply allowing Google and others to customize AMD chips for both beneficial and potentially malicious purposes, this capability also undermines AMD's secure encrypted virtualization and root-of-trust security mechanisms.
Obligatory XKCD.

Google is enhancing Android 16's Linux Terminal app to support graphical Linux applications, so Android Authority decided to put it to the test by running Doom. From the report: The Terminal app first appeared in the Android 15 QPR2 beta as a developer option, and it still remains locked behind developer settings. Since its initial public release, Google pushed a few changes that fixed issues with the installation process and added a settings menu to resize the disk, forward ports, and backup the installation. However, the biggest changes the company has been working on, which include adding hardware acceleration support and a full graphical environment, have not been pushed to any public releases.

Thankfully, since Google is working on this feature in the open, it's possible to simply compile a build of AOSP with these changes added in. This gives us the opportunity to trial upcoming features of the Android Linux Terminal app before a public release. To demonstrate, we fired up the Linux Terminal on a Pixel 9 Pro, tapped a new button on the top right to enter the Display activity, and then ran the 'weston' command to open up a graphical environment. (Weston is a reference implementation of a Wayland compositor, a modern display server protocol.)

We also went ahead and enabled hardware acceleration beforehand as well as installed Chocolate Doom, a source port of Doom, to see if it would run. Doom did run, as you can see below. It ran well, which is no surprise considering Doom can run on literal potatoes. There wasn't any audio because an audio server isn't available yet, but audio support is something that Google is still working on.

Migrating from VMware's virtualization platform could take up to four years and cost organizations between $300 and $3,000 per virtual machine, Gartner has warned in a new report. Companies running 2,000 or more virtual machines will need up to 10 full-time staff for initial assessment and another six employees for a nine-month technical evaluation, according to Gartner.

Parallels Desktop now supports running 64-bit x86 operating systems on Apple Silicon Macs through its proprietary emulation engine, enabling users to run traditional Windows and Linux distributions. However, performance is said to be "really slow." How-To Geek reports: The latest Parallels Desktop 20.2 update adds early support for x86 emulation on Apple Silicon, allowing traditional x86 PC operating systems to work on newer Mac computers. There were already apps like UTM that could do it (most of them are based on QEMU), but this feature uses Parallels' "proprietary emulation engine" paired with Apple's built-in hypervisor. [...] Parallels on Apple Silicon can now "run existing x86_64 Windows 10, Windows 11*, Windows Server 2019/2022, and some Linux distributives with UEFI BIOS via Parallels Emulator." You can also create new Windows 10 21H2 and Windows Server 2022 virtual machines if needed.

There are some big limitations. You can only run 64-bit x86 operating systems -- sorry, FreeDOS fans -- but those 64-bit operating systems can run 32-bit applications. There's also no support for USB devices, nested virtualization (so WSL2 won't work), or the Parallels hypervisor. Performance will also be "really slow," since x86 instructions have to be translated to ARM. The company said, "Windows boot time is about 2-7 minutes, depending on your hardware. Windows operating system responsiveness is also low."

"It's fair to say that by 1995, OS/2 was dead software walking," remembers a new article from the Register (which begins with a 1995 Usenet post from Gordon Letwin, Microsoft's lead architect on the OS/2 project).

But the real question is why this Microsoft-IBM collaboration on a DOS-replacing operating system ultimately lost out to Windows...? If OS/2 1.0 had been an 80386 OS, and had been able to multitask DOS apps, we think it would have been a big hit.... OS/2's initial 1980s versions were 16-bit products, at IBM's insistence. That is when the war was lost. That is when OS/2 flopped. Because its initial versions were even more crippled than the Deskpro 386...

Because OS/2 1.x flopped, Microsoft launched a product that fixed the key weakness of OS/2 1.x. That product was Windows 3, which worked perfectly acceptably on 286 machines, but if you ran the same installed copy on a 32-bit 386 PC, it worked better. Windows 3.0 could use the more sophisticated hardware of a 386 to give better multitasking of the market-dominating DOS apps...

IBM's poor planning shaped the PC industry of the 1990s more than Microsoft's successes. Windows 3.0 wasn't great, but it was good enough. It reversed people's perception of Windows after the failures of Windows 1 and Windows 2. Windows 3 achieved what OS/2 had intended to do. It transformed IBM PC compatibles from single-tasking text-only computers into graphical computers, with poor but just about usable multitasking...

Soon after Windows 3.0 turned out to be a hit, OS/2 NT was rebranded as Windows NT. Even the most ardent Linux enthusiast must c\oncede that Windows NT did quite well over three decades.
Back in 1995, the Register's author says they'd moved from OS/2 to Windows 95 "while it was still in beta.

"The UI was far superior, more hardware worked, and Doom ran much better."

An anonymous reader quotes a report from ZDNet, written by Steven Vaughan-Nichols: At KubeCon North America, SUSE announced a significant rebranding effort, several new product offerings, and the launch of SUSE AI, a secure platform for deploying and running generative AI (gen AI) applications. SUSE has renamed its entire portfolio to make product names more descriptive and customer-friendly. Notable changes include:

- Rancher, SUSE's Kubernetes offering, is now SUSE Rancher.
- Liberty Linux, the company's Red Hat Enterprise Linux (RHEL)/CentOS clone and support offering, becomes SUSE Multi Linux Support.
- Harvester is rebranded as SUSE Virtualization
- Longhorn is now SUSE Storage.

[...] Also, like everyone else, SUSE now has an AI offering: SUSE AI. This isn't an AI chatbot, like Red Hat's Lightspeed AI tool. No, it's a secure platform for deploying and running gen AI applications. This new offering addresses key challenges faced by enterprises as they move from AI experimentation to deployment, particularly in areas of security and compliance. These are SUSE AI's top features, as highlighted by Vaughan-Nichols:

1. Security by Design: SUSE AI provides security and certifications at the software infrastructure level, along with zero-trust security tools, templates, and compliance playbooks.
2. Multifaceted Trust: The platform ensures that generated data is correct and private customer and IP data remain secure. It supports deployment across various environments, including on-premise, hybrid, cloud, and air-gapped setups.
3. Choice and Flexibility: SUSE AI allows customers to select and deploy their preferred AI components and LLMs.
4. Simplified Operations: The platform provides simplified cluster operations, persistent storage, and easy access to pre-configured shared tools and services.

An anonymous reader quotes a report from GeekWire: Microsoft and Atom Computing say they've reached a new milestone in their effort to build fault-tolerant quantum computers that can show an advantage over classical computers. Microsoft says it will start delivering the computers' quantum capabilities to customers by the end of 2025, with availability via the Azure cloud service as well as through on-premises hardware. "Together, we are co-designing and building what we believe will be the world's most powerful quantum machine," Jason Zander, executive vice president at Microsoft, said in a LinkedIn posting.

Like other players in the field, Microsoft's Azure Quantum team and Atom Computing aim to capitalize on the properties of quantum systems -- where quantum bits, also known as qubits, can process multiple values simultaneously. That's in contrast to classical systems, which typically process ones and zeros to solve algorithms. Microsoft has been working with Colorado-based Atom Computing on hardware that uses the nuclear spin properties of neutral ytterbium atoms to run quantum calculations. One of the big challenges is to create a system that can correct the errors that turn up during the calculations due to quantum noise. The solution typically involves knitting together "physical qubits" to produce an array of "logical qubits" that can correct themselves.

In a paper posted to the ArXiv preprint server, members of the research team say they were able to connect 256 noisy neutral-atom qubits using Microsoft's qubit-virtualization system in such a way as to produce a system with 24 logical qubits. "This represents the highest number of entangled logical qubits on record," study co-author Krysta Svore, vice president of advanced quantum development for Microsoft Azure Quantum, said today in a blog posting. "Entanglement of the qubits is evidenced by their error rates being significantly below the 50% threshold for entanglement." Twenty of the system's logical qubits were used to perform successful computations based on the Bernstein-Vazirani algorithm, which is used as a benchmark for quantum calculations. "The logical qubits were able to produce a more accurate solution than the corresponding computation based on physical qubits," Svore said. "The ability to compute while detecting and correcting errors is a critical component to scaling to achieve scientific quantum advantage."