Monthly Archive:: May 2024
If, for some reason, you’re still using Chrome or one of the browsers that put a little hat on Chrome and call it a different browser, the time you’re going to want to consider switching to the only real alternative – Firefox – is getting closer and closer. Yesterday, Google has announced that the end of Manifest V2 is now truly here. Starting on June 3 on the Chrome Beta, Dev and Canary channels, if users still have Manifest V2 extensions installed, some will start to see a warning banner when visiting their extension management page – chrome://extensions – informing them that some (Manifest V2) extensions they have installed will soon no longer be supported. At the same time, extensions with the Featured badge that are still using Manifest V2 will lose their badge. This will be followed gradually in the coming months by the disabling of those extensions. Users will be directed to the Chrome Web Store, where they will be recommended Manifest V3 alternatives for their disabled extension. For a short time after the extensions are disabled, users will still be able to turn their Manifest V2 extensions back on, but over time, this toggle will go away as well. ↫ David Li on the Chromium blog In case you’ve been asleep at the wheel – and if you’re still using Chrome, you most likely are – Manifest V3 will heavily limit what content blockers can do, making them less effective at things like blocking ads. In a move that surprises absolutely nobody, it’s not entirely coincidental that Manifest V3 is being pushed hard by Google, the world’s largest online advertising company. While Google claims all the major content blockers have Manifest V3 versions available, the company fails to mention that they carry monikers such as “uBlock Origin Lite”, to indicate they are, well, shittier at their job than their Manifest V2 counterparts. I can’t make this any more clear: switch to Firefox. Now. While Firefox and Mozilla sure aren’t perfect, they have absolutely zero plans to phase out Manifest V2, and the proper, full versions of content blockers will continue to work. As the recent leaks have made very clear, Chrome is even more of a vehicle for user tracking and ad targeting than we already knew, and with the deprecation of Manifest V2 from Chrome, Google is limiting yet another avenue for blocking ads. OSNews has ads, and they are beyond my control, since our ads are managed by OSNews’ owner, and not by me. My position has always been clear: your computer, your rules. Nobody has any right to display ads on your computer, using your bandwidth, using your processor cycles, using your pixels. Sure, it’d be great if we could earn some income through ads, but we’d greatly prefer you become a Patreon (which removes ads) or make an individual donation to support OSNews and keep us alive that way instead.
Wayland 1.23.0 has been released. This new release includes the usual bugfixes and protocol clarifications, a number of new features few of us will really understand because we lack the expertise, and most importantly of all: OpenBSD support. That’s it. That’s the news.
Real-time Ubuntu 24.04 LTS integrates the PREEMPT_RT patch on AMD64 and ARM64. As the de-facto Linux real-time implementation, PREEMPT_RT increases predictability by modifying the existing kernel code. With time-bound responses for mission-critical latency requirements, Real-time Ubuntu 24.04 LTS provides deterministic processing to the most demanding workloads across industries, from manufacturing and automotive to the critical infrastructure of telco operators. ↫ Edoardo Barbieri at the Ubuntu blog If you need it, you need it, but it’s exclusive to Ubuntu Pro. Luckily Pro is free for personal use, so if you really need Ubuntu but with a real-time kernel – based on Linux 6.8 – there’s nothing stopping you.
Servo, the Rust-based browser engine originally started by Mozilla but since spun off into an entity under the umbrella of the Linux Foundation, has published another monthly update. As almost every month, there’s been a lot of progress on rendering tech I don’t quite understand, and further improved support for various standards. Another major focus is the ongoing font system rework, which is yielding not only vastly improved support for font rendering options, but is also reducing the memory load. The example browser included in Servo is also making progress, from reducing the amount of errors on Windows, to implementing support for using extra mouse buttons to go back and forward, and showing the link desination when hovering the mouse over a link.
Twenty-five years. A quarter century. That’s how long we’ve been working on Krita. Well, what would become Krita. It started out as KImageShop, but that name was nuked by a now long-dead German lawyer. Then it was renamed to Krayon, and that name was also nuked. Then it was renamed to Krita, and that name stuck. I only became part of Krita in 2003, when Krita was still part of KDE’s suite of productivity applications, KOffice, later renamed to Calligra… And I became maintainer of Krita in 2004, when Patrick Julien handed over the baton. That means that I’ve been around Krita for about twenty of those twenty-five years, so I’ll hope you, dear reader, will forgive me for making this a really personal post; a very large part of my life has been tied up with Krita, and it’s going to show. ↫ Krita website While it may not be as popular as something like LibreOffice due to fewer people needing it, Krita is a cornerstone application of the Linux desktop (it’s also available for Windows and macOS), and I honestly can barely believe it’s been around for this long. I’m about as far removed from being an artistic painter as a squirrel’s tail is from being a functioning propeller engine so I don’t have need for Krita, but I’m always surprised by how many people mention using it for their painting endeavours. I wish the project and its developers another successful 25 years, and they’re going to need it – Krita 5.3 is coming soon(ish), and the much more involved Krita 6.0, which makes the jump fro Qt 5 to Qt 6, is also in the works. On a personal note, I’m online acquainted with the lead maintainer of Krita, and as she alludes to at the end of the article, COVID hit her hard, and maintaining such a huge open source project isn’t easy to begin with. Much respect for keeping it up, and of course, to everyone else contributing to the project.
About a week ago I reported on a case study from Dell and FreeBSD, about Dell’s ThinOS thin client operating system, which basically consists of a proprietary Dell GUI running on top of, at the moment, FreeBSD 12 (they’re moving to FreeBSD 14 for the next ThinOS release). Well, this got me interested – I’ve always been fascinated by thin clients, and a Dell/Wyse FreeBSD ‘distribution’ is just wild enough to be interesting – so I went onto eBay, and bought a Dell thin client. More specifically, I bought a Dell OptiPlex 3000 Thin Client, which comes with an Intel Pentium Silver N6005, a four core CPU without hyperthreading, 16 GB of RAM, a 32GB eMMC storage chip with room for a small M.2 SSD, WiFi 6, Ethernet, USB 3.0, 2.0, and C ports, Bluetooth, and so on. A low-power, but still quite capable little computer that I snagged for a mere €130, which is a steal compared to the full unit price; my configuration is sold new for like €700-800. Of course, these things are sold in batches of hundreds or maybe even thousands of units, and in such volumes corporate clients get massive discounts. Still, it’s a nice deal. My model came installed with Ubuntu 20.04 LTS, which I was not at all interested in. I immediately downloaded the latest ThinOS version for my model, used Dell’s tool and instructions to create a bootable USB, and got to work. The installation process was quick and easy, and does indeed look like an automated FreeBSD installation, TUI and all. After the installation is completed, you get guided through a first-run experience to configure things like the keyboard, WiFi, and so on, and it looks rather fancy. Once I completed the first-run experience, I hit the roadblock I was expecting: in order to use ThinOS, you need a ThinOS Activation License. Since my device was originally sold with (I think) Ubuntu preinstalled, it doesn’t have a TAL in its UEFI, and the only way to push a TAL to a device is to use the Dell Wyse Management Suite. Sadly, the Dell WMS only runs on Windows, and to make matters far worse, only on Windows Server. And it gets even worse – even if I created a Windows Server VM just to run WMS, I need the Pro version, which isn’t free (the free Standard version cannot push TALs), and I’d need to buy a TAL. Aside from the Windows Server restriction, I was aware of these limitations and requirements, so I’m not in the least bit surprised. I was curious to see if buying a TAL was an easy experience, or if it’s entirely geared towards enterprise customers and silly hobbyists like me need not apply. Without a license, I can use the proprietary Dell user interface, but it seems I can’t connect to any possible VDI providers, and I can’t tell what other features might be gated at the moment. With some admittedly very mild poking and prodding, I also haven’t been able to discover any ways of ‘leaving’ Dell’s proprietary GUI to get to a terminal. I’ll do some more prodding over the coming days. I’m not entirely sure where to go from here when it comes to seeing just how much you can do with ThinOS, which was my original goal for this project. I have a feeling the pro version of the Dell Wyse Management Suite is going to be rather expensive – I can’t find any pricing information, which confirms my suspicions – so I think the journey ends here. Unless any OSNews readers have experience with this stuff, and can point me to some tips and tricks to perhaps acquire and install a TAL some other way, there won’t be a more in-depth look at Dell’s weird version of FreeBSD on OSNews. Which sucks, but was to be expected when it comes to enterprise software. Mind you, this does not mean the hardware is going to waste. Not only are there other purpose-built thin client operating systems to experiment with, it is also a full-fledged tiny x86 computer with completely silent passive cooling and a free M.2 slot, so the possibilities are endless.
Over on the GNU config-patches mailing list, Zack Weinberg is looking for help identifying a number of ancient operating systems and vendors. These are probably all either vendor or OS names from the late 1980s or early 1990s. Can anyone help me fill out the following list of things that ought to appear in testsuite/config-sub.data, if I knew what to put in place of the question marks? ???-pc533 ???-pc533-??????-sim ???-sim-??????-ultra ???-ultra-??????-unicom ???-unicom-??????-acis ???-???-aos???-triton ???-???-sysv3???-oss ???-???-sysv3???-storm-chaos ???-???-??? ↫ Zack Weinberg One of them has already been identified – “storm-chaos” turns out to have been added to binutils and/or maybe GCC in 2000, and after some digging around, John Marshall found what it’s referring to: chaos, a hobby operating system for x86 written in C. It has a long history, and after a period of inactivity came back in 2015 with a new website. Some new releases followed, with the last one being version 0.3.0 in 2019. It’s been silence since then. The others are still up for grabs to be discovered. There is some talk that the pc533 one might be a misspelling of pc532, which would refer to the “NS32K-based PC532 board running NetBSD”. This is an incredibly obscure complete system built around the NS32532, of which only around 150 were built in the early ’90s. However, Weinberg is hesitant to accept this theory without more information, since there is already code to handle the pc532, and he wants to be sure before making any changes. If there is one place on the internet outside of the GNU mailing lists that might be able to help Weinberg, it’s the OSNews audience. We have so many older people reading OSNews who have been working or otherwise active in this field for many decades, and I wouldn’t be surprised if these cryptic names make some bells ring for some of you. If one of you does e-mail a reply, be sure to mention this article – organic marketing to help keep us going!
Google is killing off a messaging service! This one is the odd “Google Business Messaging” service—basically an instant messaging client that is built into Google Maps. If you looked up a participating business in Google Maps or Google Search on a phone, the main row of buttons in the place card would read something like “Call,” “Chat,” “Directions,” and “Website.” That “Chat” button is the service we’re talking about. It would launch a full messaging interface inside the Google Maps app, and businesses were expected to use it for customer service purposes. Google’s deeply dysfunctional messaging strategy might lead people to joke about a theoretical “Google Maps Messaging” service, but it already exists and has existed for years, and now it’s being shut down. ↫ Ron Amadeo at Ars Technica When it comes to Google, it’s often hard to distinguish meme from reality.
Speaking of The Verge, its parent company Vox Media, along with The Atlantic, have signed a deal with OpenAI. Two more media companies have signed licensing agreements with OpenAI, allowing their content to be used to train its AI models and be shared inside of ChatGPT. The Atlantic and Vox Media — The Verge’s parent company — both announced deals with OpenAI on Wednesday. ↫ Emilia David at The Verge In the case of Vox Media, the deal was made and announced without informing their staff, which obviously doesn’t sit well with especially Vox’ writers. By making deals like this, upper management gets to double-dip on the fruits of their workers’ labour – first, the published content generates ad revenues, and second, OpenAI pays them to use said content for training and other purposes. And once the “AI” gets good enough, more and more of the writers will be fired, leaving only a skeleton crew of lower-paid workers to clean up the “AI” output. With this deal, the writing is on the wall for every journalist at Vox Media – you’re currently contributing to your own obsolescence, and your bosses are getting paid for it. As far as I know, OSNews’ owner, David, has not yet been contacted by OpenAI. Regardless, I’ll sell the past 20-odd years of my terrible takes for 69 million euros, after deducting Swedish taxes. And since OpenAI is run by billionaires: taxes are this thing where normal people pay a portion of their income to the government in return for various government services. It’s wild, I know.
When you launch a game on a Snapdragon on a Windows laptop, you might get an AI frame rate boost from Microsoft’s mysterious Auto Super Resolution (Auto SR) feature. But while Microsoft hasn’t fully explained how the feature works, The Verge can now confirm it’s not Qualcomm technology, not exclusive to Qualcomm’s new Snapdragon X chips, and not exclusive to specific games, either. ↫ Sean Hollister at The Verge These resolution enhancer technologies from NVIDIA, AMD, and apparently Microsoft are another great use of what we today call “AI” technologies. Of course, I wish we didn’t have to deal with several proprietary offerings but instead enjoyed several open source versions and possibly a standard to work off of, but give it some time, and we may still get there. Like I’ve said before – there’s nothing inherently wrong with “AI” technologies, as long as they’re used in ways that make sense, run locally, and most importantly, aren’t based on the wholesale theft of artists’ and programmers’ works. Unsurprisingly, the tech bros at companies like OpenAI don’t really understand the concept of “consent”, and until they do, their offerings should be deemed illegal.
The Turbo9 is a pipelined microprocessor IP written in Verilog that executes a superset of the Motorola 6809 instruction set. It is a new modern microarchitecture with 16-bit internal datapaths that balances high performance vs small area / low power. The Turbo9R with a 16-bit memory interface achieves 0.69 DMIPS/MHz which is 3.8 times faster than Motorola’s original 8-bit MC6809 implementation. It is an active graduate research project at the Department of Electrical & Computer Engineering at the University of Florida. ↫ Turbo9 GitHub page The Turbo9 is aimed at SoC sub-blocks and small mixed-signal ASIC, so it’s definitely not intended to be some sort of general purpose CPU. The reason for opting for the 6809 instead of, say, RISC-V or ARM, is that the 6809 enables a far smaller footprint due to being 16bit, which is all the target market really needs from the Turbo9. The current version of the Turbo9 is thoroughly verified and is capable of running C code. However, we still consider this version v0.9 because we are missing a few items. All the 6809 instructions and addressing modes have been implemented and tested except SYNC and CWAI. The signed versions of the Turbo9’s 16-bit divide and multiply need to be completed. Interrupts are partially implemented including SWI and Reset. ↫ Turbo9 GitHub page This is the kind of riveting content you’ll only really find on OSNews.
Few things in technology excites me more than an amazing computer I have never heard of before – especially one with pedigree. Many people take a casual glance at this machine and say, “Isn’t that an overgrown word processor?” And one could certainly think so, in part because of its keyboard-centric operation, but mostly from the utterly uncomprehending way Canon advertised it in 1987. Canon dubbed the Cat a “work processor” because of its built-in telecommunications, modem and word processor even though Jef Raskin, its designer, had intended it as a “people’s computer” that could be inexpensive, accessible and fully functional — all things he had hoped to accomplish at Apple after first launching the Macintosh project, prior to departing in 1982. Canon, however, never fully grasped the concept either. Apart from the tone-deaf marketing, Canon sold the device through their typewriter division and required the display to only show what a daisywheel printer could generate, limiting its potential as a general purpose workstation. ↫ Cameron Kaiser Wait, wait, wait. You mean to tell me there’s a unique, well-designed computer that seemed ahead of its time, sold by a printer and copier company, that failed in the market due to botched marketing and grotesque misunderstanding among management of what the device is supposed to be? What are the odds this happens twice? The Canon Cat was designed and built by Jeff Raskin’s – of Macintosh fame – company Information Appliance, Inc., and licensed to Canon. It’s an all-in-one 68000-based computer with a bitmap display, an operating system stored in ROM, and a comprehensive Forth environment easily accessible despite the device autostarting to a word processor (because Canon). Much like some of the predecessor machines Raskin had worked on before licensing the Cat to Canon, the Cat has an intriguing input method that I’d never seen before. Instead of a mouse or even cursor keys, it has two keys labeled “Leap” that are used for manipulating the text cursor. In fact, there aren’t even conventional cursor keys. The Cat has the same “leap” keys as the Swyft and SwyftCard, in a bright but tasteful pink, and they work the same way to jump to portions of the document or into other documents. You can also use them to scroll with the SHIFT key, or move by single letters, sentences or paragraphs. The LEAP keys are also how you highlight text blocks to manipulate by LEAPing to the beginning, LEAPing to the end, and then pressing them together. ↫ Cameron Kaiser The Forth programming environment is also very interesting. It was hidden in that Canon didn’t really want you to use it, but Raskin’s company made no secret of it, and it was easily accessible. It uses a special dialect of Forth, which can be used at either a traditional OK prompt, or just by typing Forth code into the word processor, highlighting it, and executing it with a keyboard shortcut, after which any output will be displayed in the word processor as well. The Canon Cat was a market failure, and hence it shouldn’t be a surprise it’s exceedingly rare. The article further details the internals, some fixes that were required and performed, and much, much more. A follow-up article will delve deeper into the software, too.
Aside from that, the company also announced Windows 11 IoT Enterprise LTSC 2024 this week. The company has also published the minimum system requirements as well as supported processor families. They have been categorized as Preferred and Optional. Interestingly, SSD has been added as a minimum system requirement, which has been a rumour about the client OS since mid-2022. ↫ Sayan Sen at NeoWin The LTSC release, which is not really supposed to be used by average consumers, is still remarkably popular. It contains a fixed feature set and gets far fewer updates than regular Windows releases, it omits otherwise stock applications like Edge, and gives its users far more control over which updates are and are not installed. LTSC also enjoys 10 years of support from Microsoft. Interestingly enough, the minimum specifications for the IoT version of LTSC do not require a TPM 2.0, unlike the regular version of Windows, which infamously does require one. I would assume that the “preferred” minimum requirements, which does require TPM 2.0, line up very well with the minimum requirements for the regular LTSC version of Windows 11. Both will become available later this year, alongside the regular release of Windows 11 24H2.
The ELF object file format is adopted by many UNIX-like operating systems. While I’ve previously delved into the control structures of ELF and its predecessors, tracing the historical evolution of ELF and its relationship with the System V ABI can be interesting in itself. ↫ MaskRay The article wasn’t lying. I had no reason to know this – and I’m pretty sure most of you didn’t either – but it turns out the standards that define ELF got caught up in the legal murkiness and nastiness of UNIX. After the dissolution of the committee governing ELF in 1995, stewardship went from one familiar name to the next, first Novell, then The Santa Cruz Operation, then Caldera which renamed itself to The SCO Group, and eventually ending up at UnXis (now Xinuos) in 2011. In 2015, the last maintainer of ELF left Xinuos, and since then, it’s been effectively unmaintained. Which is kind of wild, considering ELF is a crucial building block of virtually all UNIX and UNIX-like operating systems today. The article mentions there’s a neutral Google Group that discusses, among other things, ELF, but that, too, has seen dwindling activity. Still, that group has reached consensus on some changes; changes that are now not reflected in any of the official texts. It’s a bit of a mess. If you ever wanted to know the status of ELF as a standard, this article’s for you.
systemd uses DBus as the mechanism to interact with it. This article introduces just enough DBus concepts and the usage of busctl to communicate with systemd. These concepts should be useful when using DBus libraries. ↫ Beartama Exactly what it says on the tin.
Earlier this month, we talked about the arrival of the new CAMM2 memory module standard, specifically designed to make replaceable memory modules as fast and capable as soldered memory. There’s technically no reason for CAMM2 to not also be beneficial to desktop use, and it turns out MSI is experimenting with this. MSI on Thursday published the first image of a new desktop motherboard that supports the innovative DDR5 compression attached memory module (CAMM2). DDR5 CAMM2 modules are designed to improve upon the SO-DIMM form factor used for laptops, alleviating some of the high-speed signaling and capacity limitations of SO-DIMMs while also shaving down on the volume of space required. And while we’re eagerly awaiting to see CAMM2 show up in more laptops, its introduction in a PC motherboard comes as a bit of a surprise, since PCs aren’t nearly as space-constrained. ↫ Anton Shilov at AnandTech This MSI motherboard is a bit of an experiment, as it also contains other more experimental choices like back-mounted power connectors. While CAMM2’s space savings won’t mean much for most desktop builds, it does leave more room for CPU coolers, and it looks a bit cleaner, too.
IceWM, the venerable window manager we’ve all used at some point in our lives, has released a new version, 3.5.0. It’s a relatively minor release, so you’ve got things like a new install option which will install an extra theme, a fix for porting to NetBSD 10, translation updates, and more such small improvements. The AddressBar, a command line in the taskbar that can be summoned with ctrl+alt+space, also got some love, with file argument completion and support for the cd and pwd commands. You can compile IceWM yourself, of course, but it’ll most likely find its way into your distribution’s repository quickly enough.
But Google results are a zero-sum game. If the search engine sends traffic to one site, it has to take it from another, and the effects on the losers in this Reddit equation are just as dramatic. “Google’s just committing war on publisher websites,” Ray says. “It’s almost as if Google designed an algorithm update to specifically go after small bloggers. I’ve talked to so many people who’ve just had everything wiped out,” she says. A number of website owners and search experts who spoke to the BBC said there’s been a general shift in Google results towards websites with big established brands, and away from small and independent sites, that seems totally disconnected from the quality of the content. ↫ Thomas Germain at the BBC These stories are coming out left, right, and centre now – and the stories are heartbreaking. Websites that publish truly quality content with honest, valuable, real reviews are now not only having to combat the monster of Google’s own creation – SEO spam websites – but also Google itself, who has started downranking them in favour of fucksmith on Reddit. Add to that the various “AI” boxes and answers Google is adding to its site, and the assault on quality content is coming from all angles. I don’t look at our numbers or traffic sources, since I don’t want to be influenced by any of that stuff. I don’t think OSNews really lives or dies by a constant flow of Google results, but if we do, there’s really not much I can do about it anyway. Google Search once gaveth, and ever since that fateful day it’s mostly been Google Search taketh. I can’t control it, so I’m not going to worry about it. All I can do is keep the site updated, point out we really do need your support on Patreon and Ko-Fi – to keep OSNews running, and perhaps maybe ever going ad-free entirely – and hope for the best. I do feel for the people who still make quality content on the web, though – especially people like the ones mentioned in the linked BBC article, who set up an entire business around honest, quality reviews of something as mundane as air purifiers. It must be devastating to see all you’ve worked for destroyed by SEO spam, fucksmith on Reddit, and answers from an “AI” high on crack.
It turns out that digital rights management and its consequences extend even beyond your passing when it comes to Steam. Valve has made it clear that no, you cannot will your Steam account or games to someone else when you die. The issue of digital game inheritability gained renewed attention this week as a ResetEra poster quoted a Steam support response asking about transferring Steam account ownership via a last will and testament. “Unfortunately, Steam accounts and games are non-transferable” the response reads. “Steam Support can’t provide someone else with access to the account or merge its contents with another account. I regret to inform you that your Steam account cannot be transferred via a will.” ↫ Kyle Orland at Ars Technica My wife and I make sure we know each other’s passwords and login credentials to the most important accounts and services in our lives, since an accident can happen at any time, and we’d like to be somewhat prepared – as much as you can be, under the circumstances – for if something happens. I never even considered merging Steam accounts, but at least granting access to the person named in your will or your legal heir seems like something a service like Steam should be legally obliged to do. I don’t think Steam’s position here – which is probably par for the course – is tenable in the long-term. Over the coming years and decades, we’re going to see more and more people who grew up almost entirely online pass away, leaving behind various accounts, digital purchases, and related matters, and loved ones and heirs will want access to those. At some point over the coming decades, there’s going to be a few high-profile cases in the media about something like this, and it’s going to spur lawmakers into drafting up legislation to make account and digital goods transfers to heirs and loved ones not a courtesy, but a requirement. In the meantime, if you have a designated heir, like your children, a spouse, or whatever, make sure they can somehow gain access to your accounts and digital goods, by writing stuff down on paper and putting it somewhere safe or something similar. Again – you never know when you might… Expire.
These sources, as clearly stated in the repo’s readme, are the 8088 assembly language sources from 10th Feb 1983, and are being open-sourced for historical reference and educational purposes. This means we will not be accepting PRs that modify the source in any way. ↫ Rich Turner I’m loving all these open source releases from Microsoft, but honestly, I’d wish the pace was a little higher and we’d get to some more recent stuff. Open sourcing early versions of MS-DOS and related software is obviously great from a software preservation standpoint, but at this rate we’ll get to more influential pieces of software by the time the sun experiences its helium flash. On a related note, about a month ago Microsoft released the source code to MS-DOS 4.00. Well, we’ve now also got access to the code for MS-DOS 4.01, a bugfix release that came out very quickly after 4.00. Due to various bugs, DOS 4.00 was a relatively short-lived release, and it was replaced by DOS 4.01 just a couple of months later. Howard M. Harte (hharte), who already fixed various flaws in the official source code release of MS-DOS 4.00, managed to figure out the differences between DOS 4.00 and 4.01 — we now have access to the improved version as well! ↫ Lothar Serra Mari We’re getting a pretty complete picture of early MS-DOS source code.
Submitted by