Monthly Archive:: January 2022

While many Linux enthusiasts like to cite Linux’s stellar support for older hardware platforms, in reality that isn’t always the case. For instance with many old X.Org user-space mode-setting drivers for powering old graphics cards at least for display purposes, they can no longer even build with with modern toolchains/software components. Given the lack of bug reports around such issues, there are very likely few users trying some of these vintage hardware combinations. Longtime X.Org developer Alan Coopersmith of Oracle recently looked at going through all of the available X.Org drivers that aren’t in an archived state and seeing how they fare — with a goal of at least setting them up for simple continuous integration (CI) builds on GitLab. This is the inevitable result of hardware that was often already obscure and rare when it was new – let alone now, decades later. All we can hope for is a few people still carrying this hardware to donate either time or hardware to aid in keeping these drivers building and running.

But those laptops all have something in common with run-of-the-mill Windows PCs: a reliance on closed-source hardware and, often, the proprietary software and drivers needed to make it function. For some people, this is a tolerable trade-off. You put up with the closed hardware because it performs well, and it supports the standard software, development tools, and APIs that keep the computing world spinning. For others, it’s anathema—if you can’t see the source code for these “binary blobs,” they are inherently untrustworthy and should be used sparingly or not at all. The MNT Reform is a laptop for the latter group. It’s a crowdfunded, developed-in-the-open, extensively documented device that cares more about being open than it cares about literally any other aspect of the computing experience. Perhaps predictably, this makes for a laptop that is ideologically pure but functionally compromised. This ain’t it. I appreciate – as always – the effort, but this is not the way to go.

This paper lays out the rationale for building a completely new operating system (OS) stack. Rather than build on a single node OS together with separate cluster schedulers, distributed filesystems, and network managers, we argue that a distributed transactional DBMS should be the basis for a scalable cluster OS. We show herein that such a database OS (DBOS) can do scheduling, file management, and inter-process communication with competitive performance to existing systems. In addition, significantly better analytics can be provided as well as a dramatic reduction in code complexity through implementing OS services as standard database queries, while implementing low-latency transactions and high availability only once. I’m not even going to pretend to understand any of this.

I think I’ve mentioned occasionally that various devices, mostly cellular modems, just use the Hayes or AT command set. Recently I obtained a GPS tracking device (made by Queclink) that is, interestingly, fully configured via the Hayes command set. It’s an example of a somewhat newer trend of converging the functionality of IoT devices into the modem baseband. But what is this Hayes command set anyway? The Hayes command set is a fascinating piece of technology that’s been hanging around for far longer than most likely even its creators thought it would.

In 2021, there were no Valhall devices running mainline Linux. While a lack of devices poses an obvious obstacle to device driver development, there is no better time to write drivers than before hardware reaches end-users. Developing and distributing production-quality drivers takes time, and we don’t want users to be reliant on closed source blobs. If development doesn’t start until a device hits shelves, that device could reach “end-of-life” by the time there are mature open drivers. But with a head start, we can have drivers ready by the time devices reach end users. Let’s see how. Amazing work.

Well, that didn’t take long. There is hope for users of Google’s “legacy” free G Suite accounts. Last week, Google announced a brutal policy change—it would shut down the Google Apps accounts of users who signed up during the first several years when the service was available for free. Users who had a free G Suite account were given two options: start paying the per-user monthly fee by July 2022 or lose your account. Naturally, this move led to a huge outcry outside (and apparently inside) Google, and now, the company seems to be backing down from most of the harsher terms of the initial announcement. First, Google is launching a survey of affected G Suite users—apparently, the company is surprised by how many people this change affected. Second, it’s promising a data-migration option (including your content purchases) to a consumer account before the shutdown hits. This migration option is all we’ve ever wanted, for years now. We’ve been asking Google over and over to give us this option, because those affected had seen the writing on the wall years ago. It highlights just how incompetent Google is at customer feedback that they were at all surprised by this in any way.

Steve Jobs’s NeXT computer company made a keyboard in 1988. With no prior electronics experience, I tried to get it to work over USB. To do so, I had to go way deeper than I ever expected – all the way back over 100 years to broadcast radio standards from the 1920s. I learned tons and tons, and had a lot of fun. The things people do for the perfect keyboard.

I’ve used NixOS as the only OS on my laptop for around three years at this point. Installing it has felt sort of like a curse: on the one hand, it’s so clearly the only operating system that actually gets how package management should be done. After using it, I can’t go back to anything else. One the other hand, it’s extremely complicated constantly changing software that requires configuration with the second-worst homegrown config programming language I’ve ever used. I don’t think that NixOS is the future, but I do absolutely think that the ideas in it are, so I want to write about what I think it gets right and what it gets wrong, in the hopes that other projects can take note. As such, this post will not assume knowledge of NixOS — if you’ve used NixOS significantly, there probably isn’t anything new in here for you. NixOS is talked about a lot – but it seems impenetrable for a newcomer or outsider to get into it.

I’ve spent the past several months trying on and off to make Linux run on the Presario. The 486SX is the oldest CPU Linux still supports! I was quite hindered by my lack of any floppy disks – fortunately, I managed to get my hands on a few working ones for Christmas this year and made some headway, first getting MS-DOS 6.22 installed on the new hard disk, then messing with the Linux kernel configuration until I got it to work. And yesterday I finally got it! Here are the steps for configuring a basic kernel with Linux 5.14.8. A lack of usefulness should not be a hindrance to having fun.

Ever wondered what Microsoft’s canceled version of Windows for the Surface Duo was going to be like? Well wonder no more, as we’ve got a first hands-on look at a pre-release build from mid-2018 running on a Lumia 950. We’ve already shown you what Andromeda OS looked like in recreated mockups, so now it’s time to see the real thing running on video. The idea of using a blank canvas for writing as the homescreen is fascinating, but it’s definitely not the first time this has been tried. In fact, one sure way to ensure your mobile platform will fail, is to build it around the notepad interface. It didn’t work for PenPoint OS, it didn’t work for Apple’s Newton, and it didn’t work for any other attempts either. People simply do not want to do handwriting on a computer. It’s been tried over and over, and people just don’t like it. The only platform which has been able to sort of make handwriting work is Palm OS, but that’s a misnomer since Palm’s Graffiti was a standardised character set you had to learn – it didn’t recognise handwriting at all.

In 2020, G Suite became Google Workspace as part of a mass reorganization of the company’s apps for the “future of work.” Various plans were migrated over, and Google is now finally getting rid of the G Suite legacy free edition. “Google Apps” for businesses and schools were introduced 16 years ago and was discontinued in 2012. However, the company made no significant changes to those free accounts in the past decade, until today. In an email to administrators this morning, Google said it “will now transition all remaining users to an upgraded Google Workspace paid subscription based on your usage.” As such, Workspace’s only free plans are for Nonprofits and Education (Fundamentals). After getting free Gmail, Drive, Docs, and other apps for the past several years, companies/people will need to start paying for those Google services and the ability to use your own custom domain (instead of just gmail.com). OSNews happens to be an organisation that started out using the original Google Apps for Your Domain, and over the years, we’ve been migrated left, right, and centre through the various iterations and rebrandings of Google’s collection of services for organisations. We are one of the accounts that have been grandfathered into the current Google Workspace stuff, but we never had a choice – Google just migrated you. That doesn’t sound too bad, until you, as I have done over the past several years, find out that tons of Google services, and specific features of services, are not available to you. The reasoning here is that while Google Apps for Your Domain originally started out a service for individuals, families, and small organisations, it eventually grew into this massive corporate software suite where it perhaps makes sense to limit certain services and features. Because Google originally advertised this collection of services as much for personal accounts as it did for organisational accounts, many people, including myself, never could have anticipated our personal accounts would be forcibly turned into corporate accounts, which come with the aforementioned limitations. I can’t set calendar appointments through Google Assistant, for instance, which is annoying since we use Google Home devices. I cannot invite my fiancée to become a member of our household and control our lights and other Google Home devices through her account and phone. I cannot use Google Stadia (not that I’d want to, but still). And that’s just a small selection. Why don’t we just migrate to a regular Google account, you ask? Well, because it’s not possible. Google offers no way to either change an account from what is now Google Workspace into a personal account, nor does Google offer the ability to migrate all your accounts’ data, settings, emails, and so on from a Workspace account into a new personal account. Unless we throw everything out the window, or painstakingly move over every tiny bit of data for every single service manually, we’re going to be stuck. I don’t think it’s unreasonable of Google to ask that we old, grandfathered accounts pay for their services. That’s fine. What is not fine, however, is slowly locking us into stunted, limited accounts, after advertising it as a personal service for years.

A lot. I was the tech lead at Apple for making Mac OS X pass UNIX certification, and it was done to get Apple out of a $200M lawsuit filed by The Open Group, for use of the UNIX trademark in advertising. Fascinating bit of history.

DragonFly version 6.2 is the next step in the 6.x release series. This version has hardware support for type-2 hypervisors with NVMM, an amdgpu driver, the experimental ability to remote-mount HAMMER2 volumes, and many other changes. You can get the new release from the downloads page.

Microsoft took a while to figure out that the A: assignment is pointless as the era of Floppy drives is now over. This has been fixed in Windows 11 Build 22000 (stable). Starting with Windows 11, Device Manager no longer defaults to A: i.e it doesn’t ask you for a floppy disk for drivers (icon has also been replaced). Device Manager can now automatically detect the OS drive, so you can easily locate the driver package if you extracted the downloaded zip file to a folder on the system drive. Everything about this user experience is terrible, but at least the ditching of A: makes it slightly less terrible. I can’t believe we’re at Windows 11 in 2022, and this UI is still identical to what was first shipped in Windows 95.