OSnews

Where and when did pocket computing start? Did it start in Silicon Valley, at HP, IBM, or Apple? Did it start with the Palm Pilot, or Apple’s Newton? Not quite. No, it started in the United Kingdom, with a device that today looks more like an old calculator than a modern smartphone – but it has applications, a homescreen with apps in a grid, two memory card slots, and a whole lot more. I’m talking, of course, of Psion, the British company operating out of London that built and sold the very first personal digital assistant – a full computer small enough to slide into a pocket, with various functionalities common to mobiles phones and smartphones, like clocks, alarms, an address book, phone book, a file manager, a database, a search tool, and more. It also had an implementation of BASIC, and support for external hardware accessories and two memory card slots. The hardware The computer in question is the Psion Organiser II, a successor to – you guessed it – the Organiser, retroactively dubbed the Organiser I. The Organiser II improved upon its predecessor in a few key ways that vastly expanded its capabilities and usefulness. First and foremost, the RAM was expanded from a mere 2 kB to 8, 16, 32, or 64 KiB (or even 96 KiB, but I’ve never seen one of those), which gave developers and programmers a lot more room to play. Second, instead of a single-line display, the older Organiser II models had two lines, and later models doubled that to four lines. Third, while the original Organiser did not have an operating system, its successor came with a single-tasking operating system. Another major change between the two generations is the addition of an expansion connector for hardware accessories. Situated at the top of the device behind a tiny sliding door sits a female hardware connector in which you could plug things like an RS232 port, and devices such as speech synthesizers, telephone dialers, and more. Especially the ability to connect barcode readers and thermal printers made the Organiser II incredibly popular in a variety of industrial applications. The beating heart of all Organiser models is a Hitachi HD6303XFP processor running at 0.9 MHz, which isn’t the fastest processor in the world, but fine enough for the intended use of the device. Since opening up my Organiser II to check for the exact part and model number of the processor is out of the question (I would need to remove and deform a glued-on metal band), I don’t know which exact model my device has. Using the Organiser II I have a Psion Organiser II LZ64 model, which is one of the later models with the four-line display and 64 KiB of RAM. After sliding down the cover – its sleeping bag, as I call it – you reveal a battery door at the bottom of the device. Slide in a 9V brick battery, press the ON button, and the first thing you need to do is pick a language. After selecting your desired language, the Organiser II will start to look and feel remarkably familiar – especially considering it came out in 1986. The default screen is what can only be described as a home screen, with apps listed in a grid. You use the arrow keys to move a blinking underscore cursor around to select the app you want, and hit the EXE button on the keyboard to launch it. The software of the Organiser II has a few interesting characteristics. First of all, the ON button functions as a back and home button too – pressing it will always take you back one screen until you hit the home screen. It’s nice to know that no matter what you’re doing or no matter how much you’ve lost your way, this button will always get you back to familiar ground. Subsequent and modern mobile operating systems all have a similar button. Second, the main storage is addressed as A:, and two memory slots as B: and C:, probably in an effort to feel familiar to users of CP/M and DOS-like operating systems, which all used the same concept of drive letters. What makes this doubly interesting is that the Organiser’s drive letter convention survived and made its way into the next operating system Psion would develop, EPOC. You probably know EPOC under a different name – Symbian. The incredibly popular and successful Symbian mobile operating system used drive letters, and it can trace that all the way back to Psion’s Organiser line. Many of the applications listed on the home screen are pretty self-explanatory. Time allows you to check and set the time, including daylight savings, and the device has no problems related to Y2K. With Alarm you can set up to eight alarms that can ring daily, every hour, and so on, which will ring even when the device is off. Notes opens a simple notepad, Calc is a calculator, and so on. There are three other applications that I’d like to focus a bit more on. The first and second are Find and Save, prominently listed as the first two items on the home screen. Unlike later and modern devices, the Organiser II treats things like phone numbers, addresses, and other similar and related information a bit differently. Basically, using Save, you enter information in what is effectively a flat database, without using any specific entry fields like “Phone number” or “Last name” (with Xfiles you can copy, paste, and create additional databases alongside your main one). After saving your entry, you can then use Find to retrieve it. So, after opening Save, you get the following prompt: 12:30 Save on A: >_ You can then enter a name, address, and phone number, e.g.: T HOLWERDA123 567 89012 BEOS STREETAB1234 DANO You can then use Find to retrieve this entry using any of the entered data as a query. It’s a very simple and straightforward way of managing information,

Microsoft Corp. is working on in-house processor designs for use in server computers that run the company’s cloud services, adding to an industrywide effort to reduce reliance on Intel Corp.’s chip technology. The world’s largest software maker is using Arm Ltd. designs to produce a processor that will be used in its data centers, according to people familiar with the plans. It’s also exploring using another chip that would power some of its Surface line of personal computers. Of course they are. At this point, any major consumer platform company not working on their own ARM chips is being irresponsible.

The Altra overall is an astounding achievement – the company has managed to meet, and maybe even surpass all expectations out of this first-generation design. With one fell swoop Ampere managed to position itself as a top competitor in the server CPU market. The Arm server dream is no longer a dream, it’s here today, and it’s real. AnandTech reviews the 80-core ARM server processor from Ampere – two of them in one server, in fact – and comes away incredibly impressed.

The Google kills Android Things, its IoT OS, in January | Ars Technica, a version of Android meant for the Internet of Things. Google announced it had basically given up on the project as a general-purpose IoT operating system in 2019, but now there’s an official shutdown date thanks to a new FAQ page detailing the demise of the OS. Google promised three year of updates, but with the last update coming out in August 2019 and Android Things being launched in May 2018, Google made it to 1 year and 3 months.

Apple released macOS Big Sur 11.1 on 14 December. Although yesterday it finally posted standalone installers for the two concomitant security updates to Catalina and Mojave, no standalone updaters for Big Sur have appeared yet. Neither has it made available a standalone updater for macOS 11.0.1, which was released over a month ago. If you feel that you “have a need for individual downloads for Big Sur delta/combo updaters”, please let Apple know. In the strongest possible terms, via Feedback, Apple Support and any other means available. The lockdown continues.

Alphabet Inc.’s Google reached an illegal deal with Facebook Inc. to maintain a chokehold over the lucrative digital advertising market, according to a lawsuit filed by 10 states led by Texas. The complaint, which targets Google’s central role in the buying and selling of display ads across the web, was filed in federal court in Texas Wednesday. The regulatory onslaught is here, and I have more than enough popcorn in the house to enjoy myself.

GTK 4.0 has been released. It is impossible to summarize 4 years of development in a single post. We’ve written detailed articles about many of the new things in this release over the past year: Data transfers, Event controllers, Layout managers, Render nodes, Media playback, Scalable lists, Shaders, Accessibility. GTK is the backbone of virtually everything I do on my computers – I run GTK desktops – and I know I’m far from the only one. The benefits and improvements of a new release of this toolkit will find their way to all of the major GTK desktops, and this is the first major step in that proces.

Over 3 years ago, Google announced Project Treble, a major rearchitecting of Android designed to speed up software updates. While the architecture introduced by Project Treble has helped OEMs to speed up the delivery of major Android OS updates and monthly security patches, it has had an adverse effect on SoC providers like Qualcomm. In fact, Treble has actually increased the complexity, and thus the engineering costs, associated with providing Android OS update support for any given chipset. That has limited the length of support that Qualcomm can provide for its SoCs, but that will soon change. All Snapdragon SoCs launching with Android 11 or later—starting with the Snapdragon 888, Qualcomm will support 4 Android OS version updates as well as 4 years of security updates. That’s an additional year than they previously provided for their flagship 800-series chipsets. Since virtually all popular Android devices use Qualcomm chipsets, this is a big boon for Android users.

Neverware lets you turn old PCs and Macs into Chromebook-esque devices through its CloudReady OS. While primarily aimed at schools and enterprises, a free “Home” edition for everyone is available. Google has now acquired Neverware and CloudReady with plans to integrate it with Chrome OS. Seems like a reasonable acquisition. I’ve always found it odd that Google hasn’t tried to push Chrome OS as a downloadable, installable operating system for people to install. The only way to really experience Chrome OS is to buy a device that comes with it, which often simply doesn’t make any sense. I hope this acquisition means Google intends to offer a version of Chrome OS that we can freely download and install.

After several months of work, we are excited to announce a first proposal for a Wayland driver for Wine. At this point the proposal is in the form of an RFC (Request For Comment), in order to explore how to best move forward with the upstreaming and further development of the driver. The Wayland protocol is by design more constrained compared to more traditional display systems like X11 and win32, which brings a unique sets of challenges in the integration of Wayland with Wine. Since Wayland’s window model is not based on a single flat 2D co-ordinate space, as X11’s was, the Wayland protocol doesn’t allow apps to control their absolute position on the screen. Win32 applications heavily rely on this feature, so the Wayland driver uses a few tricks to accommodate many common cases, like transient windows (menus, tooltips etc). This is an important first step in ensuring Wine performs optimally on Wayland systems, and considering the importance of Wine for the Linux desktop due to projects like Proton, this really needs to be sorted before a full move to Wayland can be made.

As expected, Linus Torvalds today officially released Linux 5.10. Besides being the last kernel release of 2020, this is a significant milestone in that it’s also a Long Term Support (LTS) kernel to be maintained for at least the next five years and also is a huge kernel update in general with many new features. Linux 5.10 features new hardware support including early bring-up around Intel Rocket Lake and Alder Lake, continued work on Intel Gen12/Xe Graphics, a number of storage/file-system improvements, and more. It will either trickle down to your distribution, or to the mainline repository you use.

Engstrom was known as part of the “Beastie Boys,” a trio of evangelists who paved the way for Microsoft’s expansion in games in the late 1990s and early 2000s with DirectX. The expansion eventually enabled Microsoft to launch the Xbox (X signified DirectX) video game console — an enterprise that generated billions of dollars for Microsoft and made it a major player in the game industry. What a fascinating man and career.

We’ve reviewed the most powerful BBC Micro model B disc protection scheme I found, across an audit of most of the copy protected discs released for the machine. It’s clever in that you don’t need specialized hardware to create the disc, or read the disc. But you’re going to struggle to duplicate the disc. Copy protection schemes from the ’80 and early ’90s are fascinating, and this one is no exception.

I know all this because I remain a hopeless computer tinkerer who happened to come across a Quadra 700 around the start of 2020. Unlike my road test of the IIsi for Ars back in 2018, the Quadra 700 presented a tantalizing opportunity to really push the limits of early 90s desktop computing. Could this decades-old workhorse hold a candle to the multi-core behemoths of the 2020s? The IIsi turned out to be surprisingly capable; what about the Quadra 700 with its top-shelf early ‘90s specs? The Quadra 700 is such an enticing machine. Clean, elegant, and capable for its time, I’d love to play around with one today.

Microsoft has released a preview of 64bit x86 emulation for Windows on ARM. In this preview, you can install x64 apps from the Microsoft Store or from any other location of your choosing. You can try key x64-only productivity apps like Autodesk Sketchbook, as well as games like Rocket League. Other apps, like Chrome, which run today on ARM64 as 32-bit apps, can run as 64-bit using the new x64 emulation capability. These apps may benefit from having more memory when run as 64-bit emulated apps. I’m quite interested in trying out Windows on ARM out of sheer curiosity, but since I was one of the few sad sacks who bought a Surface RT on release day, I may sit this one out for a bit.

A new lawsuit brought by one of Apple’s oldest foes seeks to force the iPhone maker to allow alternatives to the App Store, the latest in a growing number of cases that aim to curb the tech giant’s power. The lawsuit was filed on Thursday by the maker of Cydia, a once-popular app store for the iPhone that launched in 2007, before Apple created its own version. The lawsuit alleges that Apple used anti-competitive means to nearly destroy Cydia, clearing the way for the App Store, which Cydia’s attorneys say has a monopoly over software distribution on iOS, Apple’s mobile operating system. “Were it not for Apple’s anticompetitive acquisition and maintenance of an illegal monopoly over iOS app distribution, users today would actually be able to choose how and where to locate and obtain iOS apps, and developers would be able to use the iOS app distributor of their choice,” the lawsuit alleges. Apple will fight lawsuits like this all the way to the Supreme Court if it has to, but I think there’s no saving this one. Eventually, somewhere, either in the US, EU, Japan, or even China, some regulator or court will demand the end of the App Store monopoly, and once the wall’s been breached in one jurisdiction, it will benefit the rest of the world.

Starting December 2020, Microsoft will begin Some Windows 10 users about to be force upgraded if they use older versions (windowslatest.com) if they don’t update their PC manually. The move comes after Microsoft announced that it’s ending support for Windows 10 version 1903, including Windows 10 Home and Windows 10 Pro. It shouldn’t be a concern for most users considering that the tech giant issued the upgrade alert two months ago. Microsoft had also confirmed that it would start forcing people to upgrade even if they don’t want to. Does anyone even know what all these version numbers even mean anymore? There’s version numbers, date-based names, build numbers – I have completely and utterly lost track of Windows’ development cycle and rollouts.

The Federal Trade Commission and more than 40 states accused Facebook on Wednesday of becoming a social media monopoly by buying up its rivals to illegally squash competition, and said the deals that turned the social network into a behemoth should be unwound. The prosecutors called for Facebook to break off Instagram and WhatsApp and for new restrictions on future deals, in what amounted to some of the most severe penalties regulators can demand. I hope it gets that far. Next on the list? Apple and Google.

Google has finally – finally – truly and honestly confirmed Fuchsia is a thing. Fuchsia is a long-term project to create a general-purpose, open source operating system, and today we are expanding Fuchsia’s open source model to welcome contributions from the public. Starting today, we are expanding Fuchsia’s open source model to make it easier for the public to engage with the project. We have created new public mailing lists for project discussions, added a governance model to clarify how strategic decisions are made, and opened up the issue tracker for public contributors to see what’s being worked on. As an open source effort, we welcome high-quality, well-tested contributions from all. There is now a process to become a member to submit patches, or a committer with full write access. In addition, we are also publishing a technical roadmap for Fuchsia to provide better insights for project direction and priorities. Some of the highlights of the roadmap are working on a driver framework for updating the kernel independently of the drivers, improving file systems for performance, and expanding the input pipeline for accessibility. It has been a very, very long time since any of the major technology companies built a new operating system from the ground up. Windows 10 is Windows NT, a project started in 1989 and first released as Windows NT 3.1 in 1993. The Linux kernel was first released in 1991. macOS grew out of NeXTSTEP, development of which started in 1985, seeing its first release in 1989. These operating systems are old. Fuchsia is truly new, and developed by one of the biggest companies in the world, and while Google has a spotty track record when it comes to corporate attention span, I doubt they’d roll out the red carpet like this after four years of sort-of-but-not-really open development if they intend to kill the entire thing two years from now. And even if they do – the code’s out there anyway. There’s a guide on how to build Fuchsia and set up an emulator (for Linux and macOS), so you can start poking around today.

The future of the CentOS Project is CentOS Stream, and over the next year we’ll be shifting focus from CentOS Linux, the rebuild of Red Hat Enterprise Linux (RHEL), to CentOS Stream, which tracks just ahead of a current RHEL release. CentOS Linux 8, as a rebuild of RHEL 8, will end at the end of 2021. CentOS Stream continues after that date, serving as the upstream (development) branch of Red Hat Enterprise Linux. A lot of people are not going to be happy with this announcement, and it seems this is the first clear insight into what IBM is planning to do with the Red Hat acquisition. Expect a new CentOS to rise to the occasion and takes its place.

I recently received my Librem 5 (Evergreen) from Purism. The Librem 5 is a smartphone that runs an otherwise standard linux kernel. However, unlike Android which also relies on the linux kernel under the hood, the Librem 5 uses a GNU userspace, adapted for mobile. This makes it more akin to your typical laptop in some ways, although the form factor still resembles a modern smartphone (at least, mostly). Here are some preliminary thoughts about the phone and how it compares to Pine64’s Pinephone, which is another phone that uses neither Android nor iOS, and relies on a GNU / Linux based OS. A detailed look at and comparison between these two smartphones that definitely share a target market. Devices like this are an excellent example of something I can now consider buying and reviewing thanks to our lovely supporters on Patreon.

Key changes in Qt 6.0 include: • Leveraging C++17• Next generation QML• New graphics architecture• Unified 2D and 3D for Qt Quick• CMake build system (with qmake still supported for applications)• Multiple improvements throughout A big release – but I’m not a programmer so I won’t pretend to try and understand all of this.

The new CPU configuration gives the new SoC a good uplift in performance, although it’s admittedly less of a jump than I had hoped for this generation of Cortex-X1 designs, and I do think Qualcomm won’t be able to retain the performance crown for this generation of Android-SoCs, with the performance gap against Apple’s SoCs also narrowing less than we had hoped for. On the GPU side, the new 35% performance uplift is extremely impressive. If Qualcomm is really able to maintain similar power figures this generation, it should allow the Snapdragon 888 to retake the performance crown in mobile, and actually retain it for the majority of 2021. At this point it feels like we’re far beyond the point of diminishing returns for smartphones, but with ARM moving to general purpose computers, there’s still a lot of performance gains to be made. I want a Linux-based competitor to Apple’s M1-based Macs, as Linux is perfectly suited for architecture transitions like this.

Ars Technica summarises and looks at the various claims made by Micro Magic about their RISC-V core. Micro Magic Inc.—a small electronic design firm in Sunnyvale, California—has produced a prototype CPU that is several times more efficient than world-leading competitors, while retaining reasonable raw performance. We first noticed Micro Magic’s claims earlier this week, when EE Times reported on the company’s new prototype CPU, which appears to be the fastest RISC-V CPU in the world. Micro Magic adviser Andy Huang claimed the CPU could produce 13,000 CoreMarks (more on that later) at 5GHz and 1.1V while also putting out 11,000 CoreMarks at 4.25GHz—the latter all while consuming only 200mW. Huang demonstrated the CPU—running on an Odroid board—to EE Times at 4.327GHz/0.8V and 5.19GHz/1.1V. Later the same week, Micro Magic announced the same CPU could produce over 8,000 CoreMarks at 3GHz while consuming only 69mW of power. I have some major reservations about all of these claims, mostly because of the lack of benchmarks that more accurately track real-world usage. Extraordinary claims requite extraordinary evidence, and I feel like some vague photos just doesn’t to the trick of convincing me. Then again, last time I said anything about an upcoming processor, I was off by a million miles, so what do I know?

This Monday, ZFS on Linux lead developer Brian Behlendorf published the OpenZFS 2.0.0 release to GitHub. Along with quite a lot of new features, the announcement brings an end to the former distinction between “ZFS on Linux” and ZFS elsewhere (for example, on FreeBSD). This move has been a long time coming—the FreeBSD community laid out its side of the roadmap two years ago—but this is the release that makes it official. A massive release.

oasis is a small linux system. It is probably quite a bit different from other Linux-based operating systems you might be familiar with, and is probably better compared to a BSD. There are many features that distinguish it from other operating systems. It’s entirely statically linked, uses various smaller, more compact alternatives to components you’d normally find in a Linux system, and it’s entirely focused on simplicity. I find it quite attractive on paper.

Since OSNews’ inception in 1997 – yes, this site is that old – a lot has changed on the internet when it comes to earning income. While for a very long time a site like OSNews could sustain itself through revenue from basic ads alone, we’re now far beyond the point where that is feasible – unless we were to introduce ever more intrusive ads, which we’re obviously not going to do. Our readers are, of course, keenly aware of how expensive it can be to run a website like OSNews, and as such, many of you have asked us over the years for methods of supporting the website financially. We’ve always had a subscriber program for an ad-free version of the site, but we never really advertised it very heavily. Today, that’s going to change. You can now support OSNews by becoming an OSNews Patreon. With your support, we can keep posting stories every single day, pay the hosting bills, write more interesting articles, access interesting hardware to review for your amusement, and possibly expand into new territories like video reviews to accompany the regular written reviews. Your support will enable us to write reviews of older, vintage devices and software like Palm PDAs, Psion devices, old operating system versions, and much more. We’ve created three tiers – Silver, Gold, and Platinum – and at each of these tiers you’ll get the ad-free version of OSNews, as well as a silver, gold, or custom comment flair to show off your status as an OSNews Patreon. All of our readers are equal, of course, but OSNews Patreons are just a little more equal. If you want to support the continued work we do, head on over to the OSNews Patreon page and become an OSNews Patreon. Thank you – all of you, not just OSNews Patreons – for supporting the site! Important note: since Patreon has ended support for their API, we are not investing engineering hours into full integration of Patreon into OSNews. This means we have to add the rewards to your OSNews account manually. As such, it may take a few hours before your rewards are added to your account, depending on time zones, availability of OSNews staff, and so on. We will obviously do our best to make this process as quick as possible, but please bear with us. Frequently (?) Asked Questions Does this mean OSNews will start putting content behind Patreon-only paywalls? No. All of the stories and articles we post will remain freely available as they always have been, and even future articles made possible through Patreon supporters will always be available to everyone. The goal of the OSNews Patreon is to support OSNews as a whole, not just a small part of it. Can you give some examples of the kinds of articles you want to write that are impossible to do without more financial support? Sure! A great example of an article – or, more likely, series of articles – that I’ve been dying to write is one about one of the last Sun UltraSPARC multiprocessor workstations, fitted with one of the later SunPCI cards. I’m a huge fan of Sun’s workstation hardware, but getting access to relatively old and outdated hardware like this is surprisingly expensive. A successful Patreon could make this a reality. I also have a massive collection of PDAs, from the late 80s all the way up to the 2000s, that I would love to write more about. That takes a lot of time, and with the support of the OSNews Patreon I might be able to set aside time from my regular job to focus more on writing articles for OSNews. There are tons of other interesting topics that require expenses too, such as SGI’s IRIX, or Psion devices, or even modern computers like the new M1-based Macs. Will you introduce more tiers and benefits in the future? Possibly. We have a few other ideas that we need to flesh out further and reconsider before making any commitments. Why is the pricing in euros, and not in dollars or Canadian rubles? The pricing is set in euros, but Patreon shows the amounts converted to your local currency. Some users may still see the euro pricing, however, for instance when using a VPN. Can I cancel my Patreon or upgrade/downgrade to a different tier? Yes. Patreon as a platform offers all of these options at any time, so you’ll never have to feel tied down or locked into or out of a certain tier.

This release comes with a new live system that leverages ZFS, compression, and replication first introduced in FuryBSD by Joe Maloney. The 20.11.28 release contains numerous improvements, including OS fixes for linuxulator to improve Linux Steam performance, an updated kernel, and GhostBSD userland updates. Userland updates include a MATE desktop upgrade to version 1.24.1, Software Station performance improvements, and numerous application updates. Does anybody have any experiences with Linuxulator? I’m quite curious about its performance compared to running the same binaries on Linux, and just how easy it is to use.

On Youtube I watched a Mac user who had bought an iMac last year. It was maxed out with 40 GB of RAM costing him about $4000. He watched in disbelief how his hyper expensive iMac was being demolished by his new M1 Mac Mini, which he had paid a measly $700 for. In real world test after test, the M1 Macs are not merely inching past top of the line Intel Macs, they are destroying them. In disbelief people have started asking how on earth this is possible? If you are one of those people, you have come to the right place. Here I plan to break it down into digestible pieces exactly what it is that Apple has done with the M1. It’s exciting to see x86 receive such a major kick in the butt, but it’s sad that the M1 is locked away and only a very, very small number of people will get to see its benefits.

In my previous post, I described running Arch on an OpenWRT router. Today, I’ll be taking it a step further and running Arch and a full LXDE installation natively on an Amazon Kindle, which can be interacted with directly using the touch screen. This is possible thanks to the Kindle’s operating system being Linux! Neat.

In a time when home PC’s were single tasking DOS boxes with 8 character file names and Ataris and Macs were single tasking GUI boxes, hampering any hacker with their glaring lack of a CLI, the Amiga was a champion of both worlds: It combined the CLI and GUI, leveraging both their strengths. But there was more to it than that, something that’s hard to convey in so many words. A long list of little things that the author believes made the Amiga great. There’s some interesting touches in there, but personally, the Amiga OS and its derivatives just do not click with me – and I’ve extensively used all of them. Not that it matters, though – there’s more than enough love for the Amiga to go around.

With Genode 20.11, we focused on the scalability of real-world application workloads, and nurtured Genode’s support for 64-bit ARM hardware. We thereby follow the overarching goal to run highly sophisticated Genode-based systems on devices of various form factors. The release notes are detailed and informative as always – a huge benefit of being a project born at and run in a university environment.

The new M1 MacBooks are fast, beautiful and silent and the hype is absolutely justified. There’s still a lot to do on the software-front to catch up, and the bugs around older iOS Simulators are especially problematic. All of that can be fixed in software and the whole industry is currently working on making the experience better, so by next year, when Apple updates the 16-inch MacBook Pro and releases the next generation of their M chip line, it should be absolutely possible to use a M1 Mac as main dev machine. For the vast majority of people, it’s going to be very hard to resist these new Macs. They’re just so far ahead of the competition in performance, power draw, battery life, and noise (or lack thereof) that any x86-based laptop just can’t compete, unless they go hardcore in on price. I’d love to have one to test and review here for OSNews, but financially that’s not in the cards for now.

This is a project providing a Linux-like OS for systems based on the Intel IA16 architecture (16-bit processors: 8086, 8088, 80188, 80186, 80286, NEC V20, V30, and compatibles). Such systems are ancient computers (IBM-PC XT/AT and clones), or more recent SBC/SoC/FPGA that reuse the huge hardware & software legacy from that popular platform. Definitely an interesting and impressive project.

A developer has successfully been able to virtualize the ARM version of Windows on Apple Silicon using the QEMU virtualizer. Apple’s M1 MacBooks have proved their worth when it comes to performance and battery efficiency. But, since these run on a custom ARM chip, it’s not yet possible to install, dual boot, or emulate Windows; which is in popular demand. Developer Alexander Graf, however, took to Twitter today to share his achievement: successfully being able to virtualize ARM Windows on Apple Silicon. Nothing too surprising, of course, but the real barrier to Windows on ARM running on M1-equipped Macs is not running Windows on M1 Macs, but Microsoft actually making the ARM version of Windows available for this very purpose.

A few weeks ago, we linked to an article that went in-depth into UEFI, and today, we have a follow-up. But the recent activity reminded me that there was one thing I couldn’t figure out how to do at the time: Enumerate all the available UEFI variables from within Windows. If you remember, Windows has API calls to get and set UEFI variable values, but not to enumerate them. So I started doing some more research to see if there was any way to do that – it’s obviously possible as the UEFI specs describe it, a UEFI shell can easily do it, and Linux does it (via a file system). My research took me to a place I wouldn’t have expected. We can always go deeper.

V7/x86 is a port of the Seventh Edition of the UNIX operating system to the x86 (i386) based PC. UNIX V7 was the last general distribution (around 1979) to come from the Research group at Bell Labs, the original home of UNIX. The port was done mostly around 1999 when “Ancient UNIX” source code licenses first became available, and was revised for release, with some enhancements, during 2006-7. The distribution includes the full UNIX Version 7 operating system, with source code, pre-built binaries, man pages, and original Version 7 documentation. Also included are a custom UNIX-style x86 assembler, an ACK-based C compiler, and several key early UCB software components such as the C shell, the editors ex and vi, and the pager more. I’m inclined to try and run this virtually, to see just how bastardised and messy UNIX has become in our current UNIX derivatives.

The FreeBSD Desktop series are about creating efficient desktop environment on the FreeBSD system. Why such series? Because telling someone who wants FreeBSD desktop to buy Mac instead is like telling someone who wants Linux desktop to buy Windows because it has WSL (Windows Subsystem for Linux) inside. This is one hell of a detailed and long series of articles – 21 of them. I’m not very well-versed in the world of BSD, and this series is making me want to give the world thing a go – just to learn and expand my horizons.

In a landmark move, the European Parliament voted today to support consumers’ Right to Repair. The resolution was adopted with 395 in favour and just 94 against, with 207 abstentions. The vote calls for the EU Commission to “develop and introduce mandatory labelling, to provide clear, immediately visible and easy-to-understand information to consumers on the estimated lifetime and reparability of a product at the time of purchase.” Good.

In this article, I will walk through the early kernel initialization process, defining the meaning of this term. System initialization is a broad topic that ranges from the platform’s hardware design all the way up to typical functions of an operating system such as handling I/O operations. It is not possible to cover the entire topic adequately within the scope of an article. In this first part I will describe the well-known AMD64: 64-bit platform. I am going to highlight a very interesting part of the initialization process the early initialization of the kernel. Later, I will compare it with ARM64. In both cases I will discuss the topic in the context of NetBSD, the operating system known for its portability. Some light reading.

Most PCs tend to boot from a primary media storage, be it a hard disk drive, or a solid-state drive, perhaps from a network, or – if all else fails – the USB stick or the boot DVD comes to the rescue… Fun, eh? Boring! Why don’t we try to boot from a record player for a change? I hope he’s using gold-plated triple-insulated Monster cables with diamond tips and uranium signal repeaters, because otherwise the superior quality of the vinyl will get lost. Would be a shame.

Earlier this year, we reviewed System76’s Lemur Pro, a laptop designed for portability and long battery life. This time around, we’re going entirely the opposite direction with the System76 Bonobo WS – a mobile workstation that looks like a laptop (if you squint), but packs some of the fastest desktop-grade hardware available on the market. Specifications System76 sent us the latest version of the Bonobo WS, with some truly bonkers specifications for what is, technically, a laptop (sort of), at a total price of $4315.22. This mobile workstation comes with an Intel Core i9-10900K, which has 10 cores and 20 threads and runs at 5.3 Ghz – and this is not a constrained mobile chip, but the full desktop processor. It’s paired with an 8GB RTX 2080 Super graphics card – which, again, is the desktop part, not the mobile version. It has 32 GB of RAM configured in dual-channel at 3200 Mhz. To top it off, I configured it with a 250 GB NVMe drive for the operating system, and an additional 1 TB NVME drive for storage and other stuff. Both of these drives have a theoretical sequential read and write speeds of 3500 MB/s and 2300 MB/s respectively. The Bonobo WS comes with a 17.3″ display, and I opted for the 1080p 144Hz version, since the 4K option was not yet available at the time of setting up the review unit. The 4K option, which I would normally recommend on a display of this size, might not make a lot of sense here since most people interested in a niche mobile workstation like this will most likely be using external displays anyway, making the splurge for the 4K option a bit moot, especially since it’s a mere 60 Hz panel. There’s a few other specifications we need to mention – specifically the weight and battery life of a massive computer like this one. The base weight is roughly 3.8 kg, and its dimensions are 43.43 × 399.03 × 319.02 mm (height × width × depth). While this machine can technically be classified as a laptop, the mobile workstation moniker is a far more apt description. This is not a machine for carrying from classroom to classroom – this is a machine that most users will use in just two, possible three places, and don’t move very often. Another reason for that is battery life. A machine with this much power requires a lot of juice, and the 97 Wh battery isn’t going to give you a lot of unplugged time to work. You’ll spend all of your time plugged into not one, but two power sockets, as this machine requires two huge power bricks. It even comes with an adorable rubber thing that ties the two power bricks together in a way that maintains some space between them for cooling and safety purposes. So not only do you have to lug around the massive machine itself, but also the two giant power bricks. As this is a mobile workstation, the ports situation is excellent. It has a USB 3.2 Gen 2×2 (ugh)/Thunderbolt 3 port (type C), 3 USB 3.2 Gen 2 (type A) ports, and a MicroSD card slot. For your external display needs, we’ve got a full-size HDMI port, 2 mini DisplayPorts (1.4) and a DisplayPort (1.4) over USB type C. Furthermore, there’s an Ethernet port, the usual audio jacks (microphone and headphones, and one also has an optical connection), and the obligatory Kensington lock. Of course, there’s wireless networking support through an Intel dual-band WiFi 6 chip, as well as Bluetooth support. Hardware The hardware of this machine is entirely dictated by its internals, since cramming this much desktop power in a computer that weighs less than 4 kg doesn’t leave you with much room to mess around. The entire design is dictated by the required cooling, and there are vents all over the place. This is not a pretty or attractive machine – but it doesn’t need to be. People who need this much mobile power to lug around don’t care about what it looks like, how thin it is, or how aluminium the aluminium is – they need this power to be properly cooled, and if that means more thickness or more vents, then please don’t skimp. If you care about form over function – which is an entirely legitimate criterion, by the way, and don’t let anybody tell you otherwise – there are other devices to choose from. While the laptop does have some RGB flourishes here and there, they’re not overly present or distracting, and the ability to switch between several colours for the keyboard lighting is very nice to have, since I find the generic white light most laptops use to not always be ideal. You can cycle through the various lighting options with a key combination. The keyboard has a little bit more key travel than I’m used to from most laptops, probably owed to its chunky size leaving more room for the keys to travel. The keys have a bit of wobble, but not enough to cause me to miss keystrokes. I am not a fan of the font used on the keyboard, but that’s a mere matter of taste. The trackpad is decent, feels fine enough, and works great with Linux (obviously). In what I first thought was a blast from the past, the laptop has physical buttons for right and left click underneath the trackpad. However, after a little bit of use, I realised just how nice it was to have actual, physical buttons, and not a diving board or – god forbid – a trackpad that only supports tapping. Of course, it’s not nearly as good as Apple’s force touch trackpad that simulates an eerily realistic click wherever you press, but it does the job just fine. That being said, though, much like with the display, I doubt many people who need a machine like this will really care. They’ll most likely not only have

Until now, most of what we know about Sega VR comes from trade show appearances, marketing materials, patent documents, and firsthand accounts. This has meant that many of unit’s the technical details have remained speculative or completely unknown. When looking back and studying hardware that pushed so many of the technical boundaries of its time, however, those details are important! Whether Sega VR achieved its many ambitious goals or not, it remains a fascinating and notable entry in VR history. In order to study hardware of this nature, if you don’t have access to the hardware or its implementation details, access to the software is often the next best thing. The software will tell you exactly what it expects of the hardware, and given those expectations, you might find that you have enough information to emulate the hardware. At the very least, you’ll have enough information to emulate a version of the hardware that conforms to the software’s expectations, and that’s exactly where we’re headed! Rebuilding the announced, but never shipped Sega VR from the early ’90s. What an effort.

If you have followed Windows 10 at all during the last few years, you know that the Windows Subsystem for Linux, or WSL for short, is the hot topic among developers. You can finally run your Linux tooling on Windows as a first class citizen, which means you no longer have to learn PowerShell or, god forbid, suffer through the ancient CMD.EXE console. Unfortunately, not everything is as rosy as it sounds. I now have to do development on Windows for Windows as part of my new role within Azure… and the fact that WSL continues to be separate from the native Windows environment shows. Even though I was quite hopeful, I cannot use WSL as my daily driver because I need to interact with “native” Windows tooling. I believe things needn’t be this way, but with the recent push for WSL 2, I think that the potential of an alternate world is now gone. But what do I mean with this? For that, we must first understand the differences between WSL 1 and WSL 2 and how the push for WSL 2 may shut some interesting paths. I was only vaguely aware of the fact WSL 2 switched to using a virtual machine instead of being an NT subsystem as WSL 1 was. There’s arguments to be made for and against either approach, but the NT subsystem approach just feels nice, more holistic to me – even if it is way more work to keep it in step with Linux.

Wayland (the protocol and architecture) is still lacking proper consideration for color management. Wayland also lacks support for high dynamic range (HDR) imagery which has been around in movie and broadcasting industry for a while now (e.g. Netflix HDR UI). While there are well established tools and workflows for how to do color management on X11, even X11 has not gained support for HDR. There were plans for it (Alex Goins, DeepColor Visuals), but as far as I know nothing really materialized from them. Right now, the only way to watch HDR content on a HDR monitor in Linux is to use the DRM KMS API directly, in other words, not use any window system, which means not using any desktop environment. Kodi is one of the very few applications that can do this at all. This is a story about starting the efforts to fix the situation on Wayland. This is a great article to read – and an important topic, too. Colour management and HDR should be a core aspect of Wayland, and these people are making it happen.

Today, Microsoft alongside our biggest silicon partners are announcing a new vision for Windows security to help ensure our customers are protected today and in the future. In collaboration with leading silicon partners AMD, Intel, and Qualcomm Technologies, Inc., we are announcing the Microsoft Pluton security processor. This chip-to-cloud security technology, pioneered in Xbox and Azure Sphere, will bring even more security advancements to future Windows PCs and signals the beginning of a journey with ecosystem and OEM partners. Pluton immediately rings a ton of alarm bells, since initiatives like this tend to not be a good thing for alternative platforms. There’s good news, though, too – Pluton will take care of firmware updates for your motherboard, which I welcome with open arms, since the current state of firmware updates where you have to use garbage OEM applications is dreadful.

Today, Microsoft is releasing the third preview of WinUI 3, and among the new features is native support for ARM64 PCs. If you’re not familiar with WinUI, you might remember it from Microsoft’s Build conference this year when the company announced Project Reunion. This is part of the firm’s plan to bring Win32 and UWP together, and do so without requiring a feature update to Windows 10. WinUI is the most important building block for an upcoming update to Windows 10 where things like Explorer and other Win32 applications will get a ‘modern’ makeover.

The Servo Project is excited to announce that it has found a new home with the Linux Foundation. Servo was incubated inside Mozilla, and served as the proof that important web components such as CSS and rendering could be implemented in Rust, with all its safety, concurrency and speed. Now it’s time for Servo to leave the nest! Code for this independent web engine is out on Github.

Apple, facing growing antitrust scrutiny over what it charges other companies for access to its App Store, said on Wednesday that it would cut in half the fee it took from the smallest app developers. Developers that brought in $1 million or less from their apps in the previous year will pay a 15 percent commission on those app sales starting next year, down from 30 percent, the company said. Good news, but it raises a whole bunch of questions – for instance, are developers going to remove their application from the store as they approach the 1 million dollar mark, since otherwise they’d have to make 1.25 million dollar the next year as to not lose out? Apple developer Twitter is confused as all heck about this. Then there’s this: The change will affect roughly 98 percent of the companies that pay Apple a commission, according to estimates from Sensor Tower, an app analytics firm. But those developers accounted for less than 5 percent of App Store revenues last year, Sensor Tower said. Apple said the new rate would affect the “vast majority” of its developers, but declined to offer specific numbers. In other words, this is a minor change for Apple, and will most likely do little to stave off antitrust concerns.

AnandTech, after benchmarking the M1 in the new Mac Mini: The M1 undisputedly outperforms the core performance of everything Intel has to offer, and battles it with AMD’s new Zen3, winning some, losing some. And in the mobile space in particular, there doesn’t seem to be an equivalent in either ST or MT performance – at least within the same power budgets. Ars Technica on the M1 in the new Mac Mini: Despite the inherent limitations of trying to benchmark a brand-new architecture on a minority-share platform, it’s obvious that the M1 SoC is exactly what Apple told us it would be—a world-leading design that marries high performance to high efficiency. When its power consumption and thermal profiles are effectively unlimited as in the Mac mini tested here—or, presumably, the actively cooled 13-inch MacBook Pro—the M1 puts the smack down on very high-performance mobile CPUs, and in many workloads, even very high-performance desktop CPUs. Apple wasn’t lying. Every review and benchmark is clear: this is insanely good hardware. The M1 is bonkers. And obviously, I was so wrong I don’t even know where to start.