OSnews

How do you boot a computer from punch cards when the computer has no operating system and no ROM? To make things worse, this computer requires special metadata called “word marks” that can’t be represented on a card. In this blog post, I describe the interesting hardware and software techniques used in the vintage IBM 1401 computer to load software from a deck of punch cards. (Among other things, half of each card contains loader code that runs as each card is read.) I go through some IBM 1401 machine code in detail, which illustrates the strangeness of the 1401’s architecture and instruction set compared to a modern machine. I simply cannot imagine what wizardry these newfangled computers must’ve felt like to the people of the ’50s, when computers first started to truly cement themselves in the public consciousness. Even though they’ve been around for twice as long, I find a world without cars far, far easier to imagine and grasp than a world without computers.

The Playstation 2 was not one of the most powerful consoles of its generation, yet it managed to achieve a level of popularity unthinkable for other companies. This machine is nowhere near as simple as the original Playstation was, but we will see why it didn’t share the same fate of previous complicated consoles. Excellent deep dive into the Playstation 2.

Today we are pleased to announce Total Cookie Protection, a major privacy advance in Firefox built into ETP Strict Mode. Total Cookie Protection confines cookies to the site where they were created, which prevents tracking companies from using these cookies to track your browsing from site to site. I don’t think anybody will be against this.

In the middle of last year I reviewed System76’s Lemur Pro, a lightweight, battery-life focused Linux laptop. I concluded that the Lemur Pro did not have any big failings, and packed a few stand-out features such as the amazing battery life and open source firmware few – if any – other laptop makers can offer. Linux user or not, the Lemur Pro was a great all-rounder that could go toe-to-toe with competing Windows laptops any day of the week. Since the publication of that review, System76 has released a new version of the Lemur Pro, focusing entirely on upgrading the internals of the machine. The casing, the keyboard, the trackpad, the display, and so on, remain unchanged, but this time around, it comes packing with Intel’s latest 11th Gen Core i5 or i7 processor – the 1135G7 or 1165G7 – and thus with Intel Iris Xe graphics, which should prove to be a massive boost over the previous generation’s UHD graphics. This won’t be a full review – other than the spec bump, nothing has changed regarding the rest of the Lemur Pro. Aside from possible changes mentioned here, the review of last year’s model still applies. As such, I decided to use the term “re-review”, which I think better describes this article. I opted for the Core i5 model this time around, since I feel the difference between it and the i7 are relatively small, especially considering the intended use case for a lightweight ultrabook such as this. This gave me some more financial room to max out the RAM at 40GB (DDR4 at 3200Mhz) and pick the 1TB SSD (M.2 PCIe gen4). The price of this specific configuration is $1613.00. The remainder of the specifications are identical to last year’s machine. It has the same fairly standard 1920×1080 14.1″ 60Hz panel, which won’t win any awards, but isn’t bad in any way either. Much like last year, I do wish System76 offered higher resolution and especially higher refresh rates as options, since once you go high refresh rate, you just can’t go back. At the same time, however, I know a lot of people are still using 60Hz displays, and wouldn’t care one bit about sticking to it. The ports situation remains the same as well, so you get one USB 3.1 Type-C Gen 2 port (these names…), two USB 3.0 Type-A ports, a MicroSD slot, an HDMI port, a barrel connector for the included charger, a combined headphone/microphone jack, and that Kensington lock thing for corporate or public environments. The Type-C port can be used a DisplayPort as well, and USB-C charging is supported as well. The stand-out feature of last year’s model makes a return here, with the 73Wh battery once again delivering astonishing battery life. I can easily go over 10 hours of normal use – some browsing, some video, some basic document work – and for this model, they’ve fixed the issue I had last year where setting the laptop to battery-saving mode would cause signficiant slowdowns in playing video. I’m sure the brand new Iris Xe graphics play a big role here, and I just leave the battery-saving mode on at all times, since I didn’t notice any downsides. Not noticing any downsides to the battery-saving mode is definitely one of the main advantages of the move to 11th Gen Intel processors and the Iris Xe GPU, but that’s not the only benefit – the laptop gets less hot too, which is great for those of us using laptops on our, you know, laps. Kicking in an open door, overall performance is improved too, with applications opening faster, complex web pages loading faster, and less fans spinning up, too. This being a full Intel machine also means it’s already, well, ready for Wayland, without having to resort to workarounds or hacks. Sadly, if using System76’s own Pop!_OS, you need to manually enable Wayland by commenting out WaylandEnable=false in /etc/gdm3/custom.conf/. Once you’ve done this, Wayland is an option in GDM and you can login. I’m taking Wayland compatibility into account when it comes to my purchasing decisions, and I figured I’m probably not alone in this. I hope System76 makes Wayland easier to enable – or even the default – on its fully Intel machines soon, because it definitely improves responsiveness and performance across the board. This is hard to quantify, and people will understandably ask for proof, but on all three machines I’m currently running in Wayland – my Dell XPS 13 9370, this Lemur Pro, and a Blackbird POWER9 machine – there’s less stutter, less tearing, better video playback performance, and lower heat output when using Wayland compared to X.org. As I mentioned at the beginning, this new Lemur Pro is a spec bump, and as such, the trackpad and keyboard are still the same. While the keyboard was already a solid one, I was less happy with the trackpad, and that remains the same here. It’s still of the diving board type, and its surface doesn’t feel nearly as nice as that of my XPS 13 – which has an excellent trackpad – or other competitors, such as the best-in-class trackpads found on Apple’s laptops. It’s not a bad trackpad, but it’s not particularly good or great either – just average. In conclusion, this new generation of the Lemur Pro is by all accounts an excellent upgrade, with better performance, less heat output and fewer fan spin-ups – all without sacrificing the excellent battery life of its predecessor. If you have one of the earlier generations Lemur Pros with the same design, there’s probably not enough here to warrant an upgrade, but if you were on the fence last year, the spec bump definitely warrants a new, fresh look. System76 took their already excellent all-rounder, and made it even better, without rocking the boat, without large changes in pricing, and still with System76’s unique open source firmware and coreboot which you’ll be hard-pressed to find anywhere else. And that’s exactly what

Solaris is still a thing, even though it’s now developed by a company nobody likes and seems to have lost all of the momentum among enthusiasts, so much so that I doubt anyone will even really care about this news item. Oracle released Solaris 11.4 almost three years ago, and is still updating it with monthly updates. Solaris 11.4 SRU30 is the latest one, released on 16 February. The update consists mainly of updates from upstream packages, but there seems to be little in the way of new features or big improvements. For those, we have to most likely wait until Solaris 11.5 or 12.0, if Oracle ever makes it that far with the formerly open source operating system that they closed back up.

KDE Plasma’s theming system is actually quite complex. It has many ways to be customized. It’s normal ever for expert users to not fully get how it works. I’ll try to explain how it works to the best of my knowledge. I’m pretty sure most KDE users here are more than aware of all of this stuff, but it’s still a good and concise overview for newcomers to KDE.

One of the most important tasks of the distribution packager is to ensure that the software shipped to our users is free of security vulnerabilities. While finding and fixing the vulnerable code is usually considered upstream’s responsibility, the packager needs to ensure that all these fixes reach the end users ASAP. With the aid of central package management and dynamic linking, the Linux distributions have pretty much perfected the deployment of security fixes. Ideally, fixing a vulnerable dependency is as simple as patching a single shared library via the distribution’s automated update system. Of course, this works only if the package in question is actually following good security practices. Over the years, many Linux distributions (at the very least, Debian, Fedora and Gentoo) have been fighting these bad practices with some success. However, today the times have changed. Today, for every 10 packages fixed, a completely new ecosystem emerges with the bad security practices at its central point. Go, Rust and to some extent Python are just a few examples of programming languages that have integrated the bad security practices into the very fabric of their existence, and recreated the same old problems in entirely new ways. This post explains the issue packagers run into very well – and it sure does look like these newer platforms are not very good citizens. I know this isn’t related, but this gives me the same feelings and reservations as Flatpak, Snap, and similar tools.

The first Android 12 developer preview hit the streets Thursday, and we’ve played with it for a day. There’s not a lot to see in this release—at least not at first. Most of the interesting bits are hidden, and the developer community is slowly enabling them. Many changes are half-finished alpha tweaks that will look different in the final release; after all, Google says these releases are for “testing and feedback.” This first release of Android 12 is meant to get some APIs and other changes in front of people for feedback, but it’s also designed to not spill the beans too much on what the final build of Android 12 will look like. With that in mind, many of the features in an earlier Android 12 leak seem right on the money. This public release is a sanitized build with a lot of stuff turned off, but the more we flip on hidden flags and catch hints in the documentation, the more this build looks like a solid halfway point between Android 11 and those leaked Android 12 screenshots. Ars always has great overviews of upcoming Android releases, and this one is no exception.

It’s time for an update on the OSNews Patreon, and the projects I’m working on as part of it. Almost three weeks ago I wrote about the Sunfire V245 delivered to my door, ready to be turned into an entirely impractical and loud UltraSPARC workstation. Last we left off, I had just received the unit, and was waiting on a few additional parts to get going – most importantly, a USB serial cable – which were delivered shortly. Why, then, hasn’t there been another article or update, showing the big server running? It turned out the machine wouldn’t boot properly. Together with John, the person who donated the machine to me, I’ve been trying to diagnose the problem, and after two weeks of troubleshooting, we seem to have isolated the probable cause of the problems. We think two replacement parts will address the problem, and John will be sending those over as soon as possible. I’ve kept all the logs and information I noted down during the ongoing troubleshooting process, and rest assured, I will write a summary about our steps and processes, to give you a glimpse into diagnosing a hardy and annoying problem that seems to be a moving target, yet is probably caused by a very much fixed part of the machine. Stay tuned! Moving on, I have two other Patreon projects planned. First, I accidentally ordered the wrong graphics cards for the SunFire V245 – they turned out to be incompatible, instead being designed for Sun’s AMD Opteron-based Ultra workstations. Since I’m now stuck with two identical Sun-branded NVIDIA Quadro workstation GPUs, I figured I might as well try and find a Sun Ultra 40 and see just how useful that beast of a workstation is in 2021. Sadly, as with many pieces of more exotic hardware, they are hard to find in Europe, and affordable machines from the United States come with very hefty shipping costs. I’m hoping for some luck on the old world continent here. Second, I intend to build a machine using nothing but parts from AliExpress. As most of you are probably aware, there’s a lively market of new Chinese-branded single and dual-socket Intel X79 and X99 motherboards on AliExpress. Countless other people on the web and YouTube have built machines around these motherboards, sporting used Xeon processors and RAM. This has become a pretty popular and mostly reliable and trustworthy market on AliExpress, and I want to explore if it’s worth it to build such a machine for people like us here on OSNews. It’s fun, exotic, cheap, and possibly stupid, so why wouldn’t you want to see me try? Please note that these plans are all subject to change, of course, and because they involve purchasing equipment from places like eBay and AliExpress, I cannot give any timelines or make any promises. Thanks to all of our Patreons – 56 of them already! – for making these projects possible, and if you want to help, support OSNews and become an OSNews Patreon!

The focus of this update is to support a number of new features that are useful for applications and games, and which have also been considered potential integration pain points for the Wayland driver. These are copy/paste, drag-and-drop and support for changing the display mode. Getting Wine properly supported on Wayland is a hugely important step in the move to Wayland, because thanks to Wine/Proton, gaming on Linux is massively viable. Having to use XWayland for games is not something I’m looking forward to.

A new court filing has revealed that, as part of the ongoing legal battle between Apple and Epic Games, Apple subpoenaed Valve Software in November 2020, demanding it provide huge amounts of commercial data about Steam sales and operations going over multiple years. Apple is demanding Valve – who is not a party to this lawsuit in any way, shape, or form – provide Apple with detailed data and information about, initially, every single game sold on Steam, including “names, prices, configurations and dates of every product on Steam, as well as detailed accounts of exactly how much money Steam makes and how it is all divvied-up”. Apple later scaled this down to just the top 600 games on Steam. Valve is not having any of it, of course. Valve’s argument goes on to explain to the court that it is not a competitor in the mobile space (this is, after all, a dispute that began with Fortnite on iOS), and makes the point that “Valve is not Epic, and Fortnite is not available on Steam.” It further says that Apple is using Valve as a shortcut to a huge amount of third party data that rightfully belongs to those third parties. The conclusion of Valve’s argument calls for the court to throw Apple’s subpoena out. “Somehow, in a dispute over mobile apps, a maker of PC games that does not compete in the mobile market or sell ‘apps’ is being portrayed as a key figure. It’s not. The extensive and highly confidential information Apple demands about a subset of the PC games available on Steam does not show the size or parameters of the relevant market and would be massively burdensome to pull together. Apple’s demands for further production should be rejected.” This feels weird and wrong in so many ways, so much so that it almost feels as if Apple is trying to gain insight into a massive market – PC games – that it is not a part of – yet. The amount and detailed nature of the data Apple is requesting is so bizarre and over the top, that the only logical conclusion I can draw is that Apple wants this data for potential competitive purposes, and not for legal purposes at all.

Today, we’re releasing the first Developer Preview of Android 12, the next version of Android, for your testing and feedback. With each version, we’re working to make the OS smarter, easier to use, and better performing, with privacy and security at the core. In Android 12 we’re also working to give you new tools for building great experiences for users. Starting with things like compatible media transcoding, which helps your app to work with the latest video formats if you don’t already support them, and easier copy/paste of rich content into your apps, like images and videos. We’re also adding privacy protections and optimizing performance to keep your apps responsive. As is standard practice by now, this first Developer Preview focuses mostly on under-the-hood and developer features, leaving the user-focused features for later releases.

You may have noticed that it’s kind of hard to find any new graphics card as of late, since supplies are limited for a whole variety of reasons. For the launch of its upcoming RTX 3060 GPU, which might prove to be a relatively affordable and capable upgrade for many, NVIDIA is going to try and do something about the shortage – by crippling the card’s suitability for cryptominers. RTX 3060 software drivers are designed to detect specific attributes of the Ethereum cryptocurrency mining algorithm, and limit the hash rate, or cryptocurrency mining efficiency, by around 50 percent. To address the specific needs of Ethereum mining, we’re announcing the NVIDIA CMP, or, Cryptocurrency Mining Processor, product line for professional mining. CMP products — which don’t do graphics — are sold through authorized partners and optimized for the best mining performance and efficiency. They don’t meet the specifications required of a GeForce GPU and, thus, don’t impact the availability of GeForce GPUs to gamers. It’s a good first step, I guess, but I feel the market is so starved at the moment this will be a drop in the ocean.

Today, we are introducing the next feature update to Windows 10, version 21H1. As people continue to rely on Windows more than ever to work, learn and have fun, we understand the importance of providing the best possible update experience to help people and organizations stay protected and productive. It is a responsibility we do not take lightly and why for the first time an H1 (first half of the calendar year) feature update release will be delivered in an optimized way using servicing technology, while continuing our semi-annual feature update cadence. In today’s blog I will cover details on how we plan to service the release, its scope, and next steps. Since I’ve lost track of the Windows release process and everything feels random and messy, I’m just going to say nothing at all.

If Microsoft had its way, Office 2021 probably wouldn’t be news at all—the Redmond giant would almost certainly prefer that everyone simply subscribe to Microsoft 365, pay a small monthly or annual fee, and get new features and fixes as they’re rolled out. For many if not most Office users, the subscription-based service is the most convenient way to get Office, even when they want to use it as locally installed software rather than doing their work in the browser and in the cloud. For the rest of us—and for those who don’t want to put up with the Byzantine procedures necessary to install Microsoft 365 apps on Remote Desktop Servers—there’s Office 2019 now, and there will be Office 2021 later this year. There will also be a new Office LTSC (Long Term Service Channel), which trades a 10 percent price hike for a guarantee of longer support periods… longer than the consumer version of Office 2021, that is. A new version of Microsoft Office used to be big news in the late ’90s and early 2000s. Now, with Office 365, LibreOffice, Google Docs, and several more than capable older standalone versions of Office, it feels like most people just don’t care anymore.

The KDE team has released Plasma 5.21, and this is one hell of a release. They’ve paid a lot of attention to presentation for this release, with visual improvements in both first and third party applications, including a new main menu (the old menu, as well as the basic cascading menu, are of course still available if you want them). On the application front, Plasma 5.21 introduces the System Monitor, a brand new resource and task manager that gives you all the information you’d ever need on your running system – and in true KDE fashion, it includes the ability to create your own personalised pages with just the information you need. Another big focus was Wayland: We have extensively refactored the compositing code in KWin and the changes should reduce latency throughout all compositing operations. We have also added a control in the compositing settings so you can choose whether you prefer lower latency or smoother animations. In addition, we have also added support for mixed-refresh-rate display setups on Wayland, e.g. you can have one screen refreshing at 144Hz and another at 60Hz, which is ideal for improving work-stations with multiple monitors. Preliminary support for multiple GPUs was also added on Wayland. There’s much more in this release, and I’m excited to try it out.

Go 1.16 has been released. The new embed package provides access to files embedded at compile time using the new //go:embed directive. Now it is easy to bundle supporting data files into your Go programs, making developing with Go even smoother. You can get started using the embed package documentation. Carl Johnson has also written a nice tutorial, “How to use Go embed”. Go 1.16 also adds macOS ARM64 support (also known as Apple silicon). Since Apple’s announcement of their new arm64 architecture, we have been working closely with them to ensure Go is fully supported; see our blog post “Go on ARM and Beyond” for more. More details can be found in the release notes.

Sailfish OS has moved into its fourth generation with the release of Sailfish OS 4.0.1 Koli. On a high-level Sailfish 4 includes several security and functionality updates, the long-awaited browser update, redesigned daily usage flow of key applications, as well as a rebooted developer experience. In particular we’re proud to boast full-scale OS-level Mobile Device Management (MDM) to enable easy and manageable end-to-end trusted corporate and governmental sector deployments. There are also a bunch of other new additions, including Android 9 app support, app sandboxing, and QR code scanning, along with improved notifications, events view, contact management and more.

VSI has made available OpenVMS V9.0-G for x86. This is the first x86 release of the year, and seventh overall, and it’s another good one with more functionality, VMware support, and a number of improvements. VSI also added five additional EAK testers (approaching 50 in all) and there may be a few more in the coming days. The porting process is progressing nicely.

Fortnite creator Epic Games has taken its fight against Apple to European Union antitrust regulators, escalating its dispute with the iPhone maker over its App Store payment system and control over app downloads. At this point I’m surprised it took them this long.

I normally deal with Linux machines. Linux is what I know and it’s what I’ve been using since I was in college. A friend of mine has been coaxing me into trying out FreeBSD, and I decided to try it out and see what it’s like. Here’s some details about my experience and what I’ve learned. Exactly what it says on the tin – and may I just say that the design and colour scheme of the website in question is extremely pleasant to the eyes.

Unikraft is a comprehensive toolchain and library operating system which builds highly specialized unikernels, software bundles that consist of a target application along with just the operating system primitives and libraries features it needs to run. Unikraft breaks the status quo of building unikernels manually, providing an automated toolchain that builds tailored unikernels that meet your (and your application’s) needs. We haven’t been paying a lot of attention to the concept of unikernels on OSNews, and I’m not sure why – possibly because they’re outside of the comfort one of a lot of people, including myself.

Last week, we mentioned that the extremely popular open source video player VLC is getting a brand-new interface in its upcoming 4.0 release, expected to debut later this year. VLC 4.0 isn’t ready for prime time use yet—but because the program is open source, adventurous users can grab nightly builds of it to take a peek at what’s coming. The screenshots we’re about to show come from the nightly build released last Friday—20210212-0431. VLC is an incredibly popular application, so any major user interface overhaul like this is sure to lead to a lot of bikeshedding.

Remember that story from two years ago, about how China had supposedly infiltrated the supply chain of Supermicro? The story was denied by American intelligence agencies and the CEOs of Apple and Amazon, but today, Bloomberg posted a follow-up piece with more sources, both anonymous and named, that the story was, in fact, real, and probably a lot bigger, too. The article lists several attacks that have taken place, all using hardware from Supermicro. Each of these distinct attacks had two things in common: China and Super Micro Computer Inc., a computer hardware maker in San Jose, California. They shared one other trait; U.S. spymasters discovered the manipulations but kept them largely secret as tthey tried to counter each one and learn more about China’s capabilities. Bloomberg is clearly sticking by and expanding its story, so this means it’s their and their sources’ word against that of giant corporations and American intelligence agencies, and we all know giant corporations and American intelligence agencies never lie. Right?

I recently came across SerenityOS when it was featured in hxp CTF and then on LiveOverflow’s YouTube channel. SerenityOS is an open source operating system written from scratch by Andreas Kling and now has a strong and active community behind it. If you’d like to learn a bit more about it then the recent CppCast episode is a good place to start, as well as all of the fantastic videos by Andreas Kling. Two of the recent videos were about writing exploits for a typed array bug in javascript, and a kernel bug in munmap. The videos were great to watch and got me thinking that it would be fun to try and find a couple of bugs that could be chained together to create a full chain exploit such as exploiting a browser bug to exploit a kernel bug to get root access. You don’t get articles like this very often – exploiting a small hobby operating system? Sure, why not.

This document proposes a mechanism for running unmodified Linux programs on Fuchsia. The programs are run in userspace process whose system interface is compatible with the Linux ABI. Rather than using the Linux kernel to implement this interface, we will implement the interface in a Fuchsia userspace program, called starnix. Largely, starnix will serve as a compatibility layer, translating requests from the Linux client program to the appropriate Fuchsia subsystem. Many of these subsystems will need to be elaborated in order to support all the functionality implied by the Linux system interface. As we expand the universe of software we wish to run on Fuchsia, we are encountering software that we wish to run on Fuchsia that we do not have the ability to recompile. For example, Android applications contain native code modules that have been compiled for Linux. In order to run this software on Fuchsia, we need to be able to run binaries without modifying them. Just more signs that Google has big plans for Fuchsia. With Google it’s always difficult to assess if they’ll go through with it, but I think they intend for Fuchsia to become the base operating system across Chrome OS, Android, their smart devices like Google Home, and everything else they might one day make. The project is too wide and deep to be anything else.

In the tests that matter, most noticeably the 3D rendering tests, we’re seeing a 3% speed-up on the Threadripper Pro compared to the regular Threadripper at the same memory frequency and sub-timings. The core frequencies were preferential on the 3990X, but the memory bandwidth of the 3995WX is obviously helping to a small degree, enough to pull ahead in our testing, along with the benefit of having access to 8x of the memory capacity as well as Pro features for proper enterprise-level administration. The downside of this comparison is the cost: the SEP difference is +$1500, or another 50%, for the Threadripper Pro 3995WX over the regular Threadripper 3990X. With this price increase, you’re not really paying +50% for the performance difference (ECC memory also costs a good amount), but the feature set. Threadripper Pro is aimed at the visual effects and rendering market, where holding 3D models in main memory is a key aspect of workflow speed as well as full-scene production. Alongside the memory capacity difference, having double the PCIe 4.0 lanes means more access to offload hardware or additional fast storage, also important tools in the visual effects space. Threadripper Pro falls very much into the bucket of ‘if you need it, this is the option to go for‘. AMD is entirely in a league of its own with these processors. I keep repeating it, but AMD’s comeback is one of the most remarkable stories in the history of technology.

Suing technology firms when they mess up is already hard, especially over privacy violations. Now, Facebook, Google, and the trade groups representing all the big tech firms are asking the Supreme Court to make it even harder for class actions to pursue cases against them. Facebook, Google, and all the others submitted a filing (PDF) to the Supreme Court this week basically arguing that if you cannot prove the specific extent to which their screwup injured you, you should not have any grounds to be part of a lawsuit against them. They are already pretty much invulnerable, but of course, they want even more protections than their sheer size, wealth, influence, and monopoly positions already give them. How surprising.

The beta for the upcoming 5.21 release of the KWinFT projects is now available. It contains a monumental rewrite of KWinFT’s windowing logic. Read on for an overview of the changes and why this rewrite was necessary. KWinFT is such a poster child for open source development. Someone wasn’t happy with KWin, a core aspect of their desktop, and put their money where their mouth is and forked it into something that they think is better. I wouldn’t be surprised to see parts of KWinFT, or even the project as a whole, make its way to become KDE’s default window manager.

There are well documented security flaws in GSM, and publicly available tools to exploit them. At the same time, it has become considerably cheaper and easier to analyze GSM traffic over the past few years. Open source tools such as gr-gsm have matured, and the community has developed methods for capturing the GSM spectrum without the need for expensive SDR radios. With less than $100 and a weekend it’s possible to capture and analyze GSM traffic. With some extra effort it’s possible to decrypt your own traffic, and depending on how your mobile provider has set up their network it may even be possible for somebody else to illegally decrypt traffic they don’t own. GSM is terrifying.

hello (also known as helloSystem) is a desktop system for creators with focus on simplicity, elegance, and usability. Its design follows the “Less, but better” philosophy. It is intended as a system for “mere mortals”, welcoming to switchers from the Mac. FreeBSD is used as the core operating system. With PC-BSD gone, it’s nice to see others step in to fill the void. This particular project was founded by Simon Peter, who also started AppImage and PureDarwin, so there’s quite a bit of pedigree here. It’s still in development and not yet ready for general use.

You think you can escape my ire today, Google? You’re no better than Apple. Case in point: Google is in hot water after banning the Google account of Andrew Spinks, the lead developer of the hit indie game Terraria. The YouTube account of Spinks’ game dev company, Re-Logic, was hit with some kind of terms-of-service violation, resulting in Google banning Spinks’ entire Google account, greatly disrupting his company’s ability to do business. After three fruitless weeks of trying to get the situation fixed, Spinks announced that his company will no longer do business with Google and that the upcoming Stadia version of Terraria is canceled. “I will not be involved with a corporation that values their customers and partners so little,” Spinks said. “Doing business with you is a liability.” This is, sadly, a very common occurrence. Google has a long history of blocking accounts for no reason at all, without giving the affected people any recourse since the company effectively has no customer service department. These cases can be absolutely devastating, causing people to lose photos, emails, access to their business financials, and god knows what else. We at OSNews use what was once called Google Apps for Your Domain (launched in 2006), only for us to be grandfathered into GSuite, which is now called Workplaces, which has led to a lot of frustration for me since GSuite accounts are locked out of a ton of Google services for no particular reason, and there’s no way to convert an existing Google account from one type to another. We were never asked if we wanted to be converted to the much more limited GSuite accounts. Google just did it. In any event, I have been pondering if we should switch to something else, but it’d be a lot of work I’d be putting on the plate of someone else – OSNews’ owner.

Mobile app developer Kosta Eleftheriou has a new calling that goes beyond software development: taking on what he sees as a rampant scam problem ruining the integrity of Apple’s App Store. Eleftheriou, who created the successful Apple Watch keyboard app FlickType, has for the last two weeks been publicly criticizing Apple for lax enforcement of its App Store rules that have allowed scam apps, as well as apps that clone popular software from other developers, to run rampant. These apps enjoy top billing in the iPhone marketplace, all thanks to glowing reviews and sterling five-star ratings that are largely fabricated, he says. I’ve been saying it for ten years: the application store model is fundamentally broken, because the owner of the application store benefits from people gaming and cheating the system. In this case, Apple profits from every scam application or subscription sold, and since the App Store constitutes a huge part of Apple’s all-important services revenue, Apple has no incentive to really tackle issues like this. Here’s what going to happen, based on my immutable pattern recognition skills: there will be more press outcry over this developer’s specific issue until Apple eventually sends out a public apology statement and sort-of addresses this specific issue. American tech media – which are deeply embedded in Apple’s ecosystem and depend on being in Apple’s good graces – will praise Apple’s response, and claim the situation has been resolved. Their next batch of review units and press invites from Apple are on their way. And a few weeks or months later, another developer suffers from the same or similar issues, rinse, repeat. The problem is not individual App Store rules or App Store reviewers having a bad day – the paradigm itself is fundamentally broken, and until the tech industry and us as users come to terms with that, these repetitive stories will keep popping up, faux press outrage and all.

Another month, another Haiku activity report. January was a busy month for OSNews’ favourite operating system project, with a lot of love sent the way of the various ports to other architectures. Work has been done on the ARM and RISC-V ports, but also on platforms you might not expect in this day and age: SPARC and PowerPC. While some may question putting any effort into these alternative platforms at all, that’s a shortsighted position – work on other platforms often aides in uncovering and fixing bugs in the code for your main platform. It also prevents code from becoming more platform-dependent than it needs to be. Amid the long list of other improvements, the one that stands out is merging support for SD/MMC cards. The SD/MMC drivers are merged. It is now possible to read and write SD and SDHC cards using controllers compatible with the SDHCI specification. This is one of those things that will make it easier to transfer files to and from your Haiku installation.

In addition to the establishing of the seL4 Foundation and adding the open-source RISC-V architecture as one of their primary architectures, the seL4 micro-kernel has been seeing a lot of work and also research into future work. Among the ambitious research goals is to create a “truly secure, general-purpose OS”. This multi-server OS would be secure, support a range of use-cases and security policies, and perform comparable to monolithic systems. Be sure to flip through the slides of the presentation in question for more information.

The Linux kernel’s floppy driver dates back to the original days of the kernel back in 1991 and is still being maintained thirty years later with the occasional fix. Somewhat surprisingly, a patch was sent in to the Linux kernel’s block subsystem ahead of the Linux 5.12 merge window around the floppy code. Floppies are awesome and I’m sure there’s tons of older machines out there – especially in corporate settings – that are still rocking a floppy drive for backwards compatibility reasons. Might as well keep the code up to snuff.

The legacy version of the Microsoft Edge, which is set to be discontinued in March, will be removed from Windows 10 with the release of Patch Tuesday updates in April. As we reported recently, Windows 10 currently comes with three different web browsers – Legacy Edge (hidden), Chromium Edge (default), and Internet Explorer (enabled). In an attempt to reduce clutter and improve security, Microsoft is removing the older browsers from the OS. I mean, on the one hand it seems like this is a reasonably move – there’s a new version of Edge, so an update will remove the old one. On the other hand, though, these are really two entirely different applications that happen to share a name, and it seems grotesque and user-hostile to just remove an entire application without even giving users the option to keep it. Sure, this concerns an outdated browser nobody uses, and that makes it easy to handwave this away, but what if this happens to an application you actually like and use?

Google is exploring an alternative to Apple Inc.’s new anti-tracking feature, the latest sign that the internet industry is slowly embracing user privacy, according to people with knowledge of the matter. Internally, the search giant is discussing how it can limit data collection and cross-app tracking on the Android operating system in a way that is less stringent than Apple’s solution, said the people, who asked not to be identified discussing private plans. Of course it’s going to be less stringent than Apple’s solution. Can’t limited ad tracking too much if ad tracking is how you make money.

The key difference between regular Ubuntu and Ubuntu Core is the underlying architecture of the system. Traditional Linux distributions rely mostly on traditional package systems—deb, in Ubuntu’s case—while Ubuntu Core relies almost entirely on Canonical’s relatively new snap package format. Ubuntu Core also gets a full 10 years of support from Canonical rather than the five years traditional Ubuntu LTS releases get. But it’s a bit more difficult to get started with, since you need an Ubuntu SSO account to even log in to a new Ubuntu Core installation in the first place. Ars takes a look at this rather unusual Ubuntu variant.

Here we go. Wayland is not ready as a 1:1 compatible Xorg replacement just yet, and maybe never will. Hence, if you are interested in existing applications to “just work” without the need for adjustments, then you may be better of not using Wayland at this point. Wayland solves no issues I have but breaks almost everything I need. And usually it stays broken, because the Wayland folks only seem to care about Gnome, and alienating everyone else in the process. DO NOT INSTALL WAYLAND! Let Wayland not destroy everything and then have other people fix the damage it caused. Or force more Red Hat/Gnome components (glib, Portals, Pipewire) on everyone! I’ll save you a read and summarise the ‘article’ so you can do something more productive, like I don’t know, cleaning your floors with a toothpick or something: “my tools and components written specifically for X and its APIs do not work under Wayland, therefore Wayland is garbage and shit”. Wayland is not X.org. Let me repeat that. Wayland is not X.org. If you need the functionality that X.org delivers, then you shouldn’t be using Wayland. This is like buying a Mac and complaining your Windows applications don’t work.

Bedrock Linux is a meta Linux distribution which allows users to mix-and-match components from other, typically incompatible distributions. Bedrock integrates these components into one largely cohesive system. You think you’ve seen everything the Linux world has to offer and nothing can you surprise you anymore, and then you run into something like this. I wonder how well this works if a Bedrock Linux installation holds up over time.

Remember HarmonyOS, the operating system Huawei claimed it had written from the ground-up? Yeah it’s just Android 10. After getting access to HarmonyOS through a grossly invasive sign-up process, firing up the SDK and emulator, and poring over the developer documents, I can’t come to any other conclusion: HarmonyOS is essentially an Android fork. The way that Huawei describes the OS to the press and in developer documents doesn’t seem to have much to do with what the company is actually shipping. The developer documents appear almost purposefully written to confuse the reader; any bit of actual shipping code to which you hold up a magnifying glass looks like Android with no major changes. The phrase “fake it till you make it” is often given as motivational advice, but I’ve never seen it applied to OS development before. If you’ve ever seen a modern Huawei Android phone, HarmonyOS is largely the same thing… with a few strings changed. So while there’s not much new to see, we can at least dissect HarmonyOS and debunk some of Huawei’s claims about its “brand-new” operating system. So nothing new under the sun here.

The first step in my crazy experiment to see if you can turn a Sun SPARC server into a workstation has been completed. Thanks to an incredibly generous donation by Jon Rushton, a reader from the UK, I’m now in possession of a SunFire V245 server (I did pay for shipping, of course). The machine has some serious specifications: Two UltraSPARC IIIi 1.5Ghz processors 8 GB of DDR1 RAM Two SAS hard drives (73GB and 140GB) Sun Raptor GFX graphics card (to be replaced by a Sun Quadro FX 3450) The machine has plenty of room for expansion, as well as the usual server features like dual power supplies, lots and lots of fans that no doubt will be incredibly loud, hot-swappable drive bays, remote management ports, and so on. Since I’m still waiting on a few more accessories I needed to purchase in order to setup and use the server – a USB serial console cable and the aforementioned more powerful GPU – I can’t turn it on and use it quite yet. While we wait on those accessories to be delivered, I figured I might as well post a story in the meantime with a bunch of photos of the server. I have a lot of learning to do here, since the server world is not a place I have ever really visited. I’m going to make stumbles along the way, but the end goal is for this server to be a usable workstation – most likely running either Linux or BSD. I can’t wait to get started.

The macOS Big Sur 11.2 kernel (XNU) source has been released here: source, tarball. My previous post on building XNU for macOS 11.0.1 described the method for compiling open source XNU for Intel Macs. This post details how to compile XNU for both Intel and Apple Silicon Macs, and how to boot the custom kernel on both platforms. Note that it is not possible to build or boot a custom XNU on Apple Silicon Macs before macOS 11.2. I doubt many people compile and run their own XNU kernels, but the fact that you can is still cool.

A group of enthusiasts are proposing a new set of graphics instructions designed for 3D graphics and media processing. These new instructions are built on the RISC-V base vector instruction set. They will add support for new data types that are graphics specific as layered extensions in the spirit of the core RISC-V instruction set architecture (ISA). Vectors, transcendental math, pixel, and textures and Z/Frame buffer operations are supported. It can be a fused CPU-GPU ISA. The group is calling it the RV64X as instructions will be 64-bit long (32 bits will not be enough to support a robust ISA). There’s a lot of activity around RISC-V, and with it being open and freely usable, a lot of – at first – cheaper, embedded uses will be taken over by RISC-V, hopefully followed by more performant use cases in the near future.

Ubuntu is going to be trying to switch over to using Wayland by default for the current Ubuntu 21.04 cycle to allow sufficient time for widespread testing and evaluation ahead of next year’s Ubuntu 22.04 LTS release. Canonical engineer Sebastien Bacher announced today they will be trying again for Ubuntu 21.04 to enable Wayland by default, four years after they originally tried but reverted back to using GNOME on X.Org for Ubuntu 18.04 LTS and since that point. Ubuntu with GNOME Shell on Wayland has been available as a non-default choice but the hope is now in 2021 they are ready to comfortably switch to Wayland. I try to use Wayland wherever possible, since the performance gains and battery life improvements are just too good to ignore. There’s still two major blockers, though – first, NVIDIA support is problematic, at best, so my main computer will remain on X until NVIDIA gets its act together. Second, my desktop environment of choice, Cinnamon, does not support Wayland and has no support coming in the pipeline, which is really disappointing. GNOME can be made usable with extensive use of extensions, and I’m seriously considering switching to it once the NVIDIA situation is sorted. My laptop already runs GNOME for this very reason.

The Linux 5.10 release included a change that is expected to significantly increase the performance of the ext4 filesystem; it goes by the name “fast commits” and introduces a new, lighter-weight journaling method. Let us look into how the feature works, who can benefit from it, and when its use may be appropriate. Better file system performance is always welcome, especially when it concerns what is probably the most common file system among desktop Linux users.

That Windows Package Manager exists at all is a big step forward, but while the service is in preview it is rather limited. At present you can use it to find and install software but removing it has to be done the old fashioned way. And who wants to do that? Finally, though, that is about to change, according to these tweets from Demitrius Nelon, a member of the Windows Package Manager team. Yes, I know it’s a preview and all that, but a package manager that cannot uninstall packages isn’t really a package manager at all, now is it?

Apple’s second computer — its first to have a case — launched in 1977, and that boxy beige Apple II was soon everywhere: in classrooms, living rooms and offices. At the vanguard of a generation of personal computers to come, it featured a particular and carefully-chosen beige. But what did that look like? Those first machines — the ones that have escaped landfills anyway — have shifted in color over 40 years. The documented public record is sketchy and confused. But I stumbled upon a way to investigate what Apple Beige was like. Fascinating bit of sleuthing, and a fun read to boot. Maybe not the most important aspect of computer history, but every bit of information we can preserve is worth it.

For our benchmark suite, almost all of our benchmarks show an uplift for the new Ryzen 5000 Mobile series, some considerably so: our compile benchmark is +12%, Corona rendering is +18%, Dolphin emulation +17%, NAMD +8%, Blender +6%. To our surprise our SPEC2006 1T benchmark is +32%, accelerated considerably by the 16 MB L3 cache, but also because these CPUs also support a higher instantaneous power turbo modes than the previous generation. This enables some competitive performance numbers against Intel’s Tiger Lake platform in single thread focused tests (AMD wins on multithread quite easily). AnandTech with the only deep dive that really matters.