OSnews

How do you write a review of a laptop when you’re struggling to find truly negative things to say? This is rarely an issue – every laptop is a compromise – but with the KDE Slimbook, I feel like I’ve hit this particular problem for the first time. A luxury, for sure, but it makes writing this review a lot harder than it’s supposed to be. First, let’s talk about Slimbook itself. Slimbook is a Linux OEM from Spain, founded in 2015, which sells various laptops and desktops with a variety of preinstalled Linux distributions to choose from (including options for no operating system, or Windows). A few years ago, Slimbook partnered with KDE to sell the KDE Slimbook – a Slimbook laptop with KDE Neon preinstalled, and the KDE logo engraved on the laptop’s lid. The current KDE Slimbook is – I think – the third generation, and the first to make the switch from Intel to AMD. With the help of the KDE organisation, Slimbook sent over a KDE Slimbook for me to review, and here’s my impressions. Power and quality The KDE Slimbook is the first modern AMD laptop I’ve tested and used, and it feels great to see AMD at the top again when it comes to laptops. The laptop Slimbook sent me comes in at € 1149, and packs the AMD Ryzen 7 4800H, which has 8 cores and 16 threads, running at a base clock of 2.9Ghz and a boost clock of 4.2Ghz. That’s more cores and threads than in any of my desktop PCs (save for the dual-processor POWER9 workstation I’m currently reviewing as well), which I still find kind of bonkers. Integrated onto the processor die is the Radeon RX Vega 7 GPU, with 7 compute units running at 1600Mhz. This obviously isn’t a gaming-oriented GPU, but it can run less intensive games in a pinch, and since it’s AMD, it works perfectly fine with Wayland, too. My unit was configured with a total of 16GB of RAM, in dual-channel mode (as it should be), running at 3200 MT/s. The motherboard has two RAM slots, both accessible, and can be configured with a maximum of 64GB of RAM – making this a rather future-proof laptop when it comes to memory. It won’t surprise you in 2021 that my review unit came with an NVMe SSD – a 256GB, PCIe 3.0 model from Gigabyte, good for a maximum sequential read speed of 1700 GB/s and a maximum sequential write speed of 1100 GB/s. This isn’t exactly the fastest SSD on the market, but Slimbook offers the option for faster – and more expensive – Samsung EVO SSDs as well. On top of that, the M.2 2280 slot is user-accessible, so you can always upgrade later. Slimbook sent me the 15.6″ model, which comes with a 15.6″ 1920×1080 60Hz panel. There is also a 14″ model with the same resolution and refresh rate. The panel is 100% sGRB, and is plenty bright and pleasant to look at. Sadly, Slimbook does not offer 1440p, 4K, or high-refresh rate options, which is a big downside in 2021. If it were up to me, I’d love to see at least a 1440p/144Hz option on both the 14″ and 15.6″, and I hope the next generation of the KDE Slimbook will offer this as an option. Battery life has been outstanding. The device loses little charge when sleeping, and I easily get 7-8 hours of regular use out of the battery. The keyboard deviates from the norm a little bit, in that it’s not the usual island chicklet type keyboard where the keys are surrounded by metal. Instead, the keys float in the keyboard deck, which instantly brought back memories of Apple’s aluminium PowerBook line. I prefer this type of keyboard design over the chicklet island design, and typing is a delight on the KDE Slimbook – the keys are stable, clicky, and requiring just the right amount of force. I also happen to think it looks really, really nice, and it has full-height inverted T arrow keys. Nice. The keyboard does have two minor niggles, though, and they both relate to the backlight. First, it takes 1-2 seconds for the keyboard backlight to come back on after it has faded off, and that’s a lot more annoying than you would think. The second issue has to do with the lettering on the keyboard. The backlight shines through the lettering on the keyboard, but in some places, it just does not shine through at all. I’m not sure what the underlying issue is – the placement of the individual LEDs or the lettering etching process – but it makes some keys hard to read when the backlight is on. The trackpad is excellent, feels smooth, pleasant, and responsive, and I haven’t experienced any issues. It’s of the diving board design, and I think it’s glass, but I’m not entirely sure. Even if it’s plastic – if it feels and works well, that’s not an issue to me. I am, however, deeply intrigued by that little LED in the top-left corner. I have no idea what it’s for, and I am fairly sure I’ve seen it come on at least a few times. I made it a point not to look it up to see if I could figure it out, but here we are, and I still have no clue. The KDE Slimbook comes packed with ports, which is a godsend in the modern world. On the left side, there’s a microSD slot, a headphone/microphone jack, a USB 3.0 port, a USB 2.0 port, an Ethernet jack, and a Kensington lock. On the right side, there’s a USB-C port (no Thunderbolt, since this is an AMD machine), a USB 3.0 port, a full-size HDMI port, and the barrel plug power connector. That’s a solid set of ports, and I have no complaints about the selection. The one big miss here is that the machine does not support charging

Apple is gearing up to roll out iOS 15 later this year. The company plans to roll it out to several of its devices, going all the way back to the iPhone 6s and iPhone 6s Plus. This will make Apple the only smartphone OEM to offer seven years of software updates to its devices. That’s a remarkable feat, considering that only a couple of OEMs on the Android side promise three years of OS upgrades and four years of security updates. To bridge this gap, the EU proposed a new law earlier this year that would force all smartphone OEMs to offer up to five years of security updates for their devices and deliver reasonably priced spare parts for the same duration. Although the EU’s new right to repair laws are yet to go into effect, the German Federal Government has now announced plans to extend the support timeline by two years. A spokesperson for Germany’s Federal Ministry of Economics recently said (via Heise Online) that the government body plans to enforce stricter rules that would require OEMs to deliver spare parts and software updates for seven years. In addition, the Federal Government wants OEMs to publish the spare part prices and not increase them over time. That’s excellent news. With Germany being such an important part of the EU, I can only hope they will set the tone for the rest of the countries to follow. Do note, however, that it’s election season in Germany, so be on the lookout for political trial balloons.

Earlier today, Microsoft pushed a promotional message to early adopters of Windows 11. The promo intended to promote the upcoming operating system’s integration with Microsoft Teams. Instead, it caused Explorer (the Windows desktop shell) to stop responding and left users without a working Start menu and taskbar. Based on the Microsoft-provided workaround, I narrowed the problem down to a registry key that contained a serialized JSON blob. The blob contained an advertisement for Microsoft Teams. The messaging and imagery in the promotion were identical to the panel you get when you press the Windows key + C on a Windows account not already set up with Teams. It’s unclear if it’s this exact promotion, however. Microsoft broke every single Windows 11 computer through an ad. Windows users – you can choose a better way.

Dubbed OMG Cables, these new variants are more capable than their counterparts. According to their creator, payloads can be triggered from over one mile away. Attackers can use them to log keystrokes and change keyboard mappings. There is also a geofencing feature, a kill switch and the ability to forge the identity of specific USB devices, like those that can leverage a specific vulnerability. While it’s unlikely us random, generic people will ever be the target of tools like this, there’s no doubt in my mind they’re being used all over the world to monitor dissidents, spy on competing companies, and so on.

A number of years ago, an 8″ disk containing Seattle Computer Products (SCP) 86-DOS 1.0 was successfully imaged. The newest files on the disk are dated April 30, 1981, making the disk the oldest complete release of what was soon to be known as PC DOS and MS-DOS, about a month older than a pre-release of PC DOS from early June 1981. While it is possible to run the 8″ disk image with 86-DOS version 1.00 under an emulator, it of course doesn’t run on a PC or any PC emulator/virtualizer. That’s a shame because most of the utilities included with SCP’s 86-DOS run under DOS just fine. In theory, it should be possible to provide a PC compatible “BIOS” component (IBMBIO.COM or IO.SYS equivalent) and run the rest of the system more or less unmodified on a PC. In practice, it can in fact be done. Behold PC-86-DOS 1.00, running from this disk image. In case you don’t know or remember, Seattle Computer Products was the company Microsoft bought the rights to DOS from, making SCP’s versions of DOS some of the oldest in existence. Getting these old versions archived and running on modern emulators is critically important for the field of computer archeology.

Apple, in a statement to various news outlets: Last month we announced plans for features intended to help protect children from predators who use communication tools to recruit and exploit them, and limit the spread of Child Sexual Abuse Material. Based on feedback from customers, advocacy groups, researchers and others, we have decided to take additional time over the coming months to collect input and make improvements before releasing these critically important child safety features. Good step, but it should be scrapped entirely. Let’s hope this is not just a case of Apple waiting for the storm to blow over, to then sneak it into a random point release.

The story of NEC’s FPUs is interesting, but as is usually the case, something led me down this path. While looking through loads of old scrap boards I found a most curious arrangement, a board with a normal unassuming V30 processor, but right next to it was another 40-pin chip, a chip with a HUGE die lid labeled D9008D, dated similar to everything else, in the 1989-1991 range curiously copyrighted 85 86 and ’87. I pulled the chip (soldered in , of course) and it sat on my desk, for a year until I decide to open the lid on it, and what did it reveal? A die that most certainly was a floating point data path. This odd chip was an FPU, and an FPU that was directly connected to the V30 CPU. Very interesting article about a very obscure topic.

Today, we are announcing the general availability of Windows Server 2022. It’s a big step forward for the operating system that is trusted by major corporations and small businesses alike to run their business and mission-critical workloads. It comes with tons of security improvements (of course), SMB compression, support for up to 48TB of memory and 2048 threads running on 64 sockets, and more.

So, I stole the bulk of my old 86sim-based Venix implementation, installed a i386 VM using bhyve on my FreeBSD/amd64 box and write a quick little test program. The test program worked, so in a fit of “why not give this a try” I ported the pcvenix.cc from 86sim to being driven from SIGSEGV in vm86 mode. Hello world quickly worked. I didn’t even know what Venix was before coming across this post, but it turns out it was a lightweight UNIX implementation for a variety of platforms.

South Korea has passed a bill written to prevent major platform owners like Google and Apple from restricting app developers to built-in payment systems, The Wall Street Journal reports. The bill is now expected to be signed into law by President Moon Jae-in, whose party championed the legislation. The law comes as a blow to Google and Apple who both require in-app purchases to flow only through their systems, instead of outside payment processors, allowing the tech giants to collect a 30 percent cut. If tech companies fail to comply with the new law, they could face fines of up to 3 percent of their South Korea revenue. This is going to spread like a wildfire, and the company’s statements regarding this new law fill me with unreasonable amounts of pleasure and schadenfreude.

Version 5.14 of the most popular operating system kernel in the world has been released. See the Linux 5.14 feature list for a comprehensive list of the changes in this new kernel version. Some of the Linux 5.14 highlights include core scheduling support, secret memory areas support with MEMFD_SECRET, continued enablement around Intel Alder Lake, Yellow Carp and Beige Goby AMD graphics support, AMD SmartShift laptop support, Raspberry Pi 400 support, and more. Linux 5.14 has the usual mix of new hardware support, improving existing features, and adding in other new kernel innovations. Coming to a distribution near you.

Windows 11 is no longer merely “coming this fall.” Microsoft will begin releasing the new operating system to the public on October 5, starting with newer PCs (and PCs being sold in stores) and then rolling out to other supported systems over the next nine or so months. The company also says that the Amazon-powered Android app support coming to Windows 11 won’t be ready for public consumption at launch; Microsoft will offer “a preview for Windows Insiders over the coming months.” Get your centered taskbar and 12th concurrently used Windows theme October 5.

Elise Blanchard goes on a deep dive of ancient GUI design and early browsers to figure out why hyperlinks are blue. But now, I find myself all consumed by the question, WHY are links blue? WHO decided to make them blue? WHEN was this decision made, and HOW has this decision made such a lasting impact? I turned to my co-workers to help me research, and we started to find the answer. Mosaic, an early browser released by Marc Andreessen and Eric Bina on January 23, 1993, had blue hyperlinks. To truly understand the origin and evolution of hyperlinks though, I took a journey through technology history and interfaces to explore how links were handled before color monitors, and how interfaces and hyperlinks rapidly evolved once color became an option.

Void is a general purpose operating system, based on the monolithic Linux kernel. Its package system allows you to quickly install, update and remove software; software is provided in binary packages or can be built directly from sources with the help of the XBPS source packages collection. Void Linux is one of my favourite distributions, but since it employs a rolling release model, I never really get the opportunity to highlight it. So, I’m picking this random day to talk about it. If you’re fairly proficient in “install and go” Linux distributions like Ubuntu, Fedora, Manjaro, etc., and want to get a better insight into a Linux system without going overboard, Void is a great choice. It’s easy to install, easy to grasp and manage manually because it eschews systemd in favour of runit, it has an excellent community, and the package repository is far, far larger than you’d expect. Void also offers both GNU libc and musl versions. Void is a bit more hands-on than e.g. Ubuntu, but not over the top like some other distributions. Setting up a Void Linux system will teach you quite a bit about how a Linux system works, but the no-nonsense, logical layout of it all means you’re not going to be overwhelmed. It also happens to be one of the few distributions that take ppc64le seriously thanks to a dedicated community, so it’s my system of choice there. It’s not for everyone, and if you just want a no-nonsense desktop experience with minimal fuss, you’re better off with Linux Mint or Manjaro or similar systems, but if you want to get your hands a little bit dirty, you can do a lot worse than Void.

Just in case you thought the Windows 11 upgrade and hardware compatibility situation couldn’t get any more confusing and complicated, Microsoft decided to do a Microsoft. This morning, Microsoft revealed a change of plan to The Verge: it won’t technically abandon those millions of PCs, because you’ll be able to manually install the downloadable Windows 11 ISO on whatever you want. The company’s also extending its official CPU compatibility list to a bunch of Intel’s most expensive Xeon workstation processors and its most expensive line of Core X desktop CPUs — and, tellingly, the less powerful Intel chip it shipped in its Surface Studio 2, so it no longer has to defend the idea of abandoning a flagship product that it still continues to sell brand-new. That sounds like a nice gesture, since it will enable anyone – even those who do not technically comply with the TPM requirements – to install Windows 11, even if it has to be a fresh installation (which you should probably do with new Windows versions anyway). However, it turns out there’s a major caveat here. While yes, Microsoft will allow you to install Windows 11 on unsupported hardware, these installations might not get updates – not even security updates. First and perhaps most important, Microsoft informed us after we published this story that if your computer doesn’t meet the system requirements, it may not be entitled to get Windows Updates, even security ones. We’re asking Microsoft for clarification on that now. But secondly, it still sounds like Microsoft will be encouraging millions of people to replace their perfectly good Windows PCs. Other than yet another theme third parties aren’t going to adopt, there’s not a whole lot in Windows 11 as it is, and with all this confusion around upgrades, supported hardware, and access to updates, Windows 10 users are probably better off sticking with Windows 10 for a little while longer. Or, you know, switch to an operating system that doesn’t treat its users like garbage.

Known to be “functional, free and secure by default”, the OpenBSD operating system has played an important role in open source for more than a quarter century. It has also been fairly central to what I have done for the last two decades and some. What follows is my personal view of what life with OpenBSD has been like, with an emphasis on moments and developments that I feel made life, or at least my life, better. Good article about an operating system that seems to just do its thing, and do it well.

Arm is widely regarded as the most important semiconductor IP firm. Their IP ships in billions of new chips every year from phones, cars, microcontrollers, Amazon servers, and even Intel’s latest IPU. Originally it was a British owned and headquartered company, but SoftBank acquired the firm in 2016. They proceeded to plow money into Arm Holdings to develop deep pushes into the internet of things, automotive, and server. Part of their push was also to go hard into China and become the dominant CPU supplier in all segments of the market. As part of the emphasis on the Chinese market, SoftBank succumbed to pressure and formed a joint venture. In the new joint venture, Arm Holdings, the SoftBank subsidiary sold a 51% stake of the company to a consortium of Chinese investors for paltry $775M. This venture has the exclusive right to license Arm’s IP within China. Within 2 years, the venture went rogue. Recently, they gave a presentation to the industry about rebranding, developing their own IP, and striking their own independently operated path. This is not the first time the Chinese government – through its companies and investors – has gained access to a large amount of silicon IP (both VIA and AMD fell for this too). Not that I care much for Arm here – they were blinded by greed, and will pay the price – but hopefully this opens the eyes of other companies in similar positions.

Edward Snowden: Having read thousands upon thousands of remarks on this growing scandal, it has become clear to me that many understand it doesn’t matter, but few if any have been willing to actually say it. Speaking candidly, if that’s still allowed, that’s the way it always goes when someone of institutional significance launches a campaign to defend an indefensible intrusion into our private spaces. They make a mad dash to the supposed high ground, from which they speak in low, solemn tones about their moral mission before fervently invoking the dread spectre of the Four Horsemen of the Infopocalypse, warning that only a dubious amulet—or suspicious software update—can save us from the most threatening members of our species. Suddenly, everybody with a principled objection is forced to preface their concern with apologetic throat-clearing and the establishment of bonafides: I lost a friend when the towers came down, however… As a parent, I understand this is a real problem, but… An excellent and scathing takedown of Apple’s planned backdoors.

Linux distributions like Debian fulfill an important function in the FOSS ecosystem – they are system integrators that take existing free and open source software projects and adapt them where necessary to work well together. They also make it possible for users to install more software in an easy and consistent way and with some degree of quality control and review. One of the consequences of this model is that the distribution package often lags behind upstream releases. This is especially true for distributions that have tighter integration and standardization (such as Debian), and often new upstream code is only imported irregularly because it is a manual process – both updating the package, but also making sure that it still works together well with the rest of the system. However, there have been developments over the last decade that make it easier to import new upstream releases into Debian packages. An interesting look at what the Debian project is doing to make it easier for upstream code to be packaged as proper .deb packages.

Currently, you would probably rank Google’s offerings behind every other big-tech competitor. A lack of any kind of top-down messaging leadership at Google has led to a decade and a half of messaging purgatory, with Google both unable to leave the space altogether and unable to commit to a single product. While companies like Facebook and Salesforce invest tens of billions of dollars into a lone messaging app, Google seems content only to spin up an innumerable number of under-funded, unstable side projects led by job-hopping project managers. There have been periods when Google briefly produced a good messaging solution, but the constant shutdowns, focus-shifting, and sabotage of established products have stopped Google from carrying much of these user bases—or user goodwill—forward into the present day. Because no single company has ever failed at something this badly, for this long, with this many different products (and because it has barely been a month since the rollout of Google Chat), the time has come to outline the history of Google messaging. Prepare yourselves, dear readers, for a non-stop rollercoaster of new product launches, neglected established products, unexpected shut-downs, and legions of confused, frustrated, and exiled users. This is delightfully depressing.

For the last few weeks, I’ve been running CalyxOS. It is the latest in Free/Open Source mobile phone operating systems that I’ve used. This post is a summary of my experience using FLOSS mobile OSes and what my experience can tell us not only about phones, but Free/Open Source OSes in general. An excellent rundown of the various options in this space, and I’m tempted to see if I can make this step in the near future too. Cutting Google out of my mobile phone would be quite, quite welcome.

More owners of the first-generation Nest Hub are Google Fuchsia update is rolling out widely to 1st-gen Nest Hubs as it expands beyond the Preview program. Back in May, Google formally released Fuchsia, its effort to develop a “not Linux” operating system from scratch, which has been years in the making. The first device to receive the new OS was Google’s 2018 smart display, the Nest Hub — not to be confused with the second generation Nest Hub with sleep tracking released earlier this year — taking it permanently off of the existing Linux based “Cast OS” without negatively affecting the UI or experience. The rollout continues.

Samsung has confirmed that it will stop showing ads in default apps including Samsung Weather, Samsung Pay, and Samsung Theme. It follows comments made by its mobile chief TM Roh in an internal town hall meeting reported by Yonhap. “Samsung has made a decision to cease the advertisement on proprietary apps including Samsung Weather, Samsung Pay, and Samsung Theme,” the company said in a statement given to The Verge. “The update will be ready by later this year.” I never got any of these ads on my Samsung Galaxy Note 10+, but I’d be absolutely livid if I did. I’m not going to commend Samsung for doing the absolutely bare minimum here and not show ads on €1000 devices. Dear lord.

Dedication asks each of its adherents to have faith even as time and energy pass through from one year to the next. Dedication brings with it a variety of challenges, but also rewards. Dedication is something most people claim to have, but few readily exhibit it in the face of adversity. As of today, Aug. 18, 2021, the Haiku Project is celebrating two decades of dedication, marking the 20th anniversary of the founding of the Haiku operating system and the start of this ride to save, maintain, and expand upon the BeOS legacy it spawned from. Congratulations to the Haiku project and all of its contributors.

The Intel 386 SX CPU quickly replaced the 286 CPU in the early 1990s. For a time, it was a very popular CPU, especially for people who were wanting to run Microsoft Windows. Yet the two CPUs run at nearly identical speed. So what was the big deal? The 286 vs 386SX argument could be confusing in 1991, and it’s not much clearer today. Here at OSNews we pride ourselves in pointing you to the most relevant, up-to-date buying advice available on the internet.

Earlier this month, Apple unveiled a system that would scan iPhone and iPad photos for child sexual abuse material (CSAM). The announcement sparked a civil liberties firestorm, and Apple’s own employees have been expressing alarm. The company insists reservations about the system are rooted in “misunderstandings.” We disagree. We wrote the only peer-reviewed publication on how to build a system like Apple’s — and we concluded the technology was dangerous. We’re not concerned because we misunderstand how Apple’s system works. The problem is, we understand exactly how it works. There’s now so much evidence from credible, trustworthy people and organisations that Apple’s system is bad and dangerous, that I find it hard to believe there are still people cheering Apple on.

I at least peruse if not review in depth the vast majority of all those PRs, and every time I see a PR that is likely to impact performance, I make a note of it in a running log, giving me a long list of improvements I can revisit when it’s blog time. That made this August a little daunting, as I sat down to write this post and was faced with the list I’d curated of almost 550 PRs. Don’t worry, I don’t cover all of them here, but grab a large mug of your favorite hot beverage, and settle in: this post takes a rip-roarin’ tour through ~400 PRs that, all together, significantly improve .NET performance for .NET 6. You might want to get some coffee.

The theme for this release has been adding new functionality to the MATE Desktop while maintaining the look and feel that we all know and love. While all the added features are surely quite exciting we also did not forget to do tons of bugfixing, modernising the code base and optimizing the performance. MATE is one of the two great alternatives for people who find GNOME 3 and later unpleasant (the other being Cinnamon, my DE of choice).

In Windows 11, Microsoft has changed the way you set default apps. Like Windows 10, there’s a prompt that appears when you install a new browser and open a web link for the first time. It’s the only opportunity to easily switch browsers, though. Unless you tick “always use this app,” the default will never be changed. It’s incredibly easy to forget to toggle the “always use this app” option, and simply launch the browser you want from this prompt and never see this default choice again when you click web links. Microsoft has changed the way default apps are assigned in Windows 11, which means you now have to set defaults by file or link type instead of a single switch. In the case of Chrome, that means changing the default file type for HTM, HTML, PDF, SHTML, SVG, WEBP, XHT, XHTML, FTP, HTTP, and HTTPS. That’s what you get when you use proprietary operating systems. Windows and macOS are not designed for you; they’re designed for Microsoft and Apple, respectively.

Researchers have produced a collision in iOS’s built-in hash function, raising new concerns about the integrity of Apple’s CSAM-scanning system. The flaw affects the hashing system, called NeuralHash, which allows Apple to check for exact matches of known child-abuse imagery without possessing any of the images or gleaning any information about non-matching pictures. On Tuesday, a GitHub user called Asuhariet Ygvar posted code for a reconstructed Python version of NeuralHash, which he claimed to have reverse-engineered from previous versions of iOS. The GitHub post also includes instructions on how to extract the NeuralMatch files from a current macOS or iOS build. Once the code was public, more significant attacks were quickly discovered. A user called Cory Cornelius produced a collision in the algorithm: two images that generate the same hash. If the findings hold up, it will be a significant failure in the cryptography underlying Apple’s new system. American tech media and bloggers have been shoving the valid concerns aside ever since Apple announced this new backdoor into iOS, and it’s barely been a week and we already see major tentpoles come crashing down. I try not to swear on OSNews, but there’s no other way to describe this than as a giant clusterfuck of epic proportions.

Speaking of Debian, there’s even bigger news than a new Debian GNU/Hurd release – Debian 11.0 is out and about! This release contains over 11,294 new packages for a total count of 59,551 packages, along with a significant reduction of over 9,519 packages which were marked as obsolete and removed. 42,821 packages were updated and 5,434 packages remained unchanged. As always, Debian release are big, and they are hugely important as they serve as the base for some of the most popular Linux distributions out there.

It is with huge pleasure that the Debian GNU/Hurd team announces the release of Debian GNU/Hurd 2021. This is a snapshot of Debian “sid” at the time of the stable Debian “bullseye” release (August 2021), so it is mostly based on the same sources. It is not an official Debian release, but it is an official Debian GNU/Hurd port release. In this release, the port of go has been completed, experimental support for APIC, SMP, and 64bit has been added, and more.

Asahi Linux, the effort to port Linux to Apple’s new M1 SoC, has posted its second progress report. It’s been a long time since the last update! In all honesty, the first Progress Report set the bar a little bit too high, and I found it difficult to sit down and put together monthly reports that would do it justice. So, going forward, we’re going to be providing shorter-form updates while striving to keep a monthly schedule. That said, a lot has happened in the past few months, so strap in for a bigger update this time! Quite a lot of detail in here, and lots of insights into the reverse engineering processes the developers are implementing.

A great intro to a classic platform by way of emulation and optionally even adapting a real physical keyboard: Back in the late 80s and through the 90s, Unix workstations were super powerful, super cool, and super expensive. If you were making 3D graphics or developing applications, you wanted a high-performance workstation and Sun made some of the best ones. But unless you worked for a huge company, university, or government, they were probably too expensive. More than twenty years later, we have much more powerful and affordable computers, so let’s emulate the old systems and see what it was like to run some of the coolest computers you could buy in the 90s. This is another in the series from the same author as the recently linked virtual NeXT machine, that also includes an entry for a virtual BeBox to experience BeOS.

This is the Commodore 64 KERNAL, modified to run on the Atari 8-bit line of computers. They’re practically the same machine; why didn’t someone try this 30 years ago? No time like the present.

Apple employees have flooded an Apple internal Slack channel with more than 800 messages on the plan announced a week ago, workers who asked not to be identified told Reuters. Many expressed worries that the feature could be exploited by repressive governments looking to find other material for censorship or arrests, according to workers who saw the days-long thread. Past security changes at Apple have also prompted concern among employees, but the volume and duration of the new debate is surprising, the workers said. Some posters worried that Apple is damaging its leading reputation for protecting privacy. It’s a complete 180 from Apple’s behaviour and statements (in western markets) – of course employees are going to be worried. I’ve been warning for years that Apple’s position on privacy was nothing more than a marketing ploy, and now Apple employees, too, get a taste of their own medicine that they’ve been selling in China and various other totalitarian regimes.

Hello Windows Insiders! Today we are rolling out the first set of updates for several apps that come included as part of Windows 11. The following app updates are rolling out to Windows Insiders in the Dev Channel at first. Microsoft has updated some of the default Windows applications – Snipping Tool, Calculator, and Mail & Calendar.

Their legislation would bar the companies from certain conduct that would tend to force developers to use their app stores or payment systems. It also would obligate the companies to protect app developers’ rights to tell consumers about lower prices and offer competitive pricing. It would effectively allow apps to be loaded onto Apple users’ devices outside of the company’s official app store. There’s so much movement on this front, I highly doubt Apple and Google will be able to stop it. This is one of the very, very rare cases where both sides of the political spectrum seem to somewhat agree, and I hope they can make it stick. It’s definitely not enough, but it’s a step in the right direction. I’m an extremist – all source code should be freely available (not necessarily open source – just viewable), to give consumers and society as a whole the ability to ensure they’re not being spied on, lied to, or endangered by foreign entities or corporate trickery. If copyright is good enough for writers, artists, and musicians, it’s damn well good enough for programmers. With how vital computers and software have become – woven into the fabric of our society – we as people should be able to see and check what those threads are doing and where they’re going to and coming from. Corporations have shown time and time again that they are not trustworthy entities and that they do not have society’s best interests at heart, and we need tools to bring the balance of power back – black boxes of code are dangerous.

So imagine my surprise when I dug around in a quarter-century-old archive to find a .zip file containing something that purported to be the original executable of Labyrinth. Surely such an ancient piece of code – written for Windows 3.1 – wouldn’t launch? Well, after a bit of fiddling with the Windows compatibility settings, I was shocked – and extremely pleased – to see that, yes, it most certainly did. It shouldn’t be surprising that a piece of good Windows code from 30 years ago still runs on Windows 10 today, and yet, it always is.

An operating system I’ve been writing since ~June 2017. Although it’s a long shot (and very optimistic), I ultimately intend it to replace Linux and Windows as a desktop operating system. Very optimistic, but there’s quite a few things here already. The code is on gitlab, where you can find more information, too.

MorphOS 3.15 ram-handler contains a bug that when unlucky may results in the RAM: root directory to appear to contain many duplicate entries. Multiple users had reported this over the years, but until recently the root cause of this issue had eluded us. Due to recent developments, the bug has finally been located and fixed (thanks to AngryTom for help!). Fixed ram-handler will be released as the part of the future MorphOS 3.16 release. Meanwhile you can install the following patch that fixes the problem for MorphOS 3.15. I know this isn’t a major new release or anything, but it’s rather rare and interesting to see a small, standalone update like this being release for a small, alternative operating system. Usually, these get rolled into major new releases or nightlies, so I found this interesting.

In 1985 Steve Jobs resigned from Apple and founded NeXT Inc. in order to build the NeXT Computer. It was ahead of its time and had amazing features thanks to the NeXTSTEP operating system, most famously used at CERN by Sir Tim Berners-Lee to create the World Wide Web. NeXTSTEP later became OPENSTEP and when Apple acquired NeXT in 1997, they used it as the basis for Mac OS X and iOS. If you’ve done any Mac or iOS programming, you’ve seen the echoes of NeXTSTEP in the type names – NSObject, NSString, NSDictionary, and many others all come directly from NeXT (NS = NeXTSTEP). These computers cost about as much as a new car when they first came out, so they were out of reach for most people. What was it like to use a top of the line system in the early 90s? Let’s build our own and find out! Exactly as it says on the tin. A fun few hours.

Valve’s “Steam Deck” handheld PC has caused quite a stir among PC gaming geeks, but the biggest shakeup might not be its Nintendo Switch-like form factor. The software running inside of it is the real surprise. Why does the Steam Deck run Linux? Blame Windows. The Steam Deck and the software inside of it are the culmination of a nearly decade-long “hedging strategy” embarked upon by Valve chief Gabe Newell and company many moons ago, when Microsoft tried exerting more control over developers with Windows 8. But it’s also the next phase of Valve’s escape plan. Also, Windows is simply a terrible choice for the Steam Deck. The base model only has 64GB of storage, and Windows 10 will easily take up two-thirds of that.

Dr. Neal Krawetz, one of the leading experts in the area of computer forensics research, digital photo analysis, and related topics, has penned a blog post in which he takes apart Apple’s recent announcement and the technology behind it. He actually has a lot of experience with the very problem Apple is trying to deal with, since he is the creator of FotoForensics, and files CSAM reports to the National Center for Missing and Exploited Children (NCMEC) every day. In fact, he files more reports than Apple, and knows all the ins and outs of all the technologies involved – including reverse-engineering Microsoft’s PhotoDNA, the perceptual hash algorithm NCMEC and Apple are using. The reason he had to reverse-engineer PhotoDNA is that NCMEC refused to countersign the NDA’s they wanted Krawetz to sign, eventually not responding to his requests altogether. Krawetz is one of the more prolific reporters of CSAM material (number 40 out of 168 in total in 2020). According to him, PhotoDNA is not as sophisticated as Apple’s and Microsoft’s documentation and claims make it out to be. Perhaps there is a reason that they don’t want really technical people looking at PhotoDNA. Microsoft says that the “PhotoDNA hash is not reversible”. That’s not true. PhotoDNA hashes can be projected into a 26×26 grayscale image that is only a little blurry. 26×26 is larger than most desktop icons; it’s enough detail to recognize people and objects. Reversing a PhotoDNA hash is no more complicated than solving a 26×26 Sudoku puzzle; a task well-suited for computers. The other major component of Apple’s system, an AI perceptual hash called a NeuralHash, is problematic too. The experts Apple cites have zero background in privacy or law, and while Apple’s whitepaper is “overly technical”, it “doesn’t give enough information for someone to confirm the implementation”. Furthermore, Krawetz “calls bullshit” on Apple’s claim that there is a 1 in 1 trillion error rate. After a detailed analysis of the numbers involved, he concludes: What is the real error rate? We don’t know. Apple doesn’t seem to know. And since they don’t know, they appear to have just thrown out a really big number. As far as I can tell, Apple’s claim of “1 in 1 trillion” is a baseless estimate. In this regard, Apple has provided misleading support for their algorithm and misleading accuracy rates. Krawetz also takes aim at the step where Apple manually reviews possible CP material by sending them from the device in question to Apple itself. After discussing this with his attorney, he concludes: The laws related to CSAM are very explicit. 18 U.S. Code § 2252 states that knowingly transferring CSAM material is a felony. (The only exception, in 2258A, is when it is reported to NCMEC.) In this case, Apple has a very strong reason to believe they are transferring CSAM material, and they are sending it to Apple — not NCMEC. It does not matter that Apple will then check it and forward it to NCMEC. 18 U.S.C. § 2258A is specific: the data can only be sent to NCMEC. (With 2258A, it is illegal for a service provider to turn over CP photos to the police or the FBI; you can only send it to NCMEC. Then NCMEC will contact the police or FBI.) What Apple has detailed is the intentional distribution (to Apple), collection (at Apple), and access (viewing at Apple) of material that they strongly have reason to believe is CSAM. As it was explained to me by my attorney, that is a felony. This whole thing looks, feels, and smells like a terribly designed system that is not only prone to errors, but also easily exploitable by people and governments with bad intentions. It also seems to be highly illegal, making one wonder why Apple were to put this out in the first place. Krawetz hints at why Apple is building this system earlier in this article: Apple’s devices rename pictures in a way that is very distinct. (Filename ballistics spots it really well.) Based on the number of reports that I’ve submitted to NCMEC, where the image appears to have touched Apple’s devices or services, I think that Apple has a very large CP/CSAM problem. I think this might be the real reason Apple is building this system.

Every good operating system needs a web browser, especially as more and more apps move to the web. To that end, Google is preparing to bring the full Google Chrome browser experience to Fuchsia OS. This was inevitable, of course. As the article notes, Fuchsia already has the Chrome engine to display web content if needed, and now they are bringing the whole actual browser over as well. Just another step in the long journey to replace the underpinnings of Android and Chrome OS.

Apple also addressed the hypothetical possibility of a particular region in the world deciding to corrupt a safety organization in an attempt to abuse the system, noting that the system’s first layer of protection is an undisclosed threshold before a user is flagged for having inappropriate imagery. Even if the threshold is exceeded, Apple said its manual review process would serve as an additional barrier and confirm the absence of known CSAM imagery. Apple said it would ultimately not report the flagged user to NCMEC or law enforcement agencies and that the system would still be working exactly as designed. After yesterday’s news and today’s responses from experts, here’s a recap: Apple is going to scan all photos on every iPhone to see if any of them match against a dataset of photos – that Apple itself hasn’t verified – given to them by the authorities of countries in which this is rolled out, with final checks being done by (third party) reviewers who are most likely traumatized, overworked, underpaid, and easily infiltrated. What could possibly go wrong? Today, Apple sent out an internal memo to Apple employees about this new scanning system. In it, they added a statement by Marita Rodriguez, executive director of strategic partnerships at the National Center for Missing and Exploited Children, and one of the choice quotes: I know it’s been a long day and that many of you probably haven’t slept in 24 hours. We know that the days to come will be filled with the screeching voices of the minority. Apple signed off on that quote. They think those of us worried about invasive technologies like this and the power backdoors like this would give to totalitarian regimes all over the world are the “screeching voices of the minority”. No wonder this company enjoys working with the most brutal regimes in the world.

A large number of security and privacy experts, legal experts, and more, in an open letter to Apple: On August 5th, 2021, Apple Inc. announced new technological measures meant to apply across virtually all of its devices under the umbrella of “Expanded Protections for Children”. While child exploitation is a serious problem, and while efforts to combat it are almost unquestionably well-intentioned, Apple’s proposal introduces a backdoor that threatens to undermine fundamental privacy protections for all users of Apple products. The open letter contains tons of arguments, scenarios, and examples from experts about just how bad this technology is, and just how easily it can be abused.

Oliver Kuederle, who works with the image hashing technology used by Apple’s new technology that’s going to scan the photos on your iOS device continuously, explains that it is far, far from foolproof: Perceptual hashes are messy. The simple fact that image data is reduced to a small number of bits leads to collisions and therefore false positives. When such algorithms are used to detect criminal activities, especially at Apple scale, many innocent people can potentially face serious problems. My company’s customers are slightly inconvenienced by the failures of perceptual hashes (we have a UI in place that lets them make manual corrections). But when it comes to CSAM detection and its failure potential, that’s a whole different ball game. Needless to say, I’m quite worried about this. This is just one of the many, many problems with what Apple announced yesterday.

Airyx is a new open-source desktop operating system that aims to provide a similar experience and compatibility with macOS on x86-64 systems. It builds on the solid foundations of FreeBSD, existing open source packages in the same space, and new code to fill the gaps. Airyx aims to feel sleek, stable, familiar and intuitive, handle your daily tasks, and provide as much compatibility as possible with the commercial OS that inspired it. An ambitious but interesting effort, that seems to align quite well with helloSystem.

Solène created a week-long personal computing challenge around old computers. I chose to use an Amiga for the week. In this issue I write about my experience, and what modern computing lost when Commodore died. I also want to show some of the things you can do with an Amiga or even an emulator if you’d like to try. I’ve tried to get into the Amiga-like operating systems – MorphOS, AROS, Amiga OS 4 – but the platform just doesn’t suit me. I find them convoluted, incomprehensible, and frustratingly difficult to use. Not that it matters – I’m not here to ruin the Amiga community’s party – but if they want to sustain that community instead of having it die out as their user numbers dwindle due to old age, they might want to consider making their operating systems a little less… Obtuse.