bww Bitwise works has released a port of GCC 9.2 compiler to OS/2 Warp, ArcaOS and eComStation. This is a new milestone for OS/2 software development that allows the community to port more open source software to this platform. The project port is available at github.
Guest post by Anonymous
2020-02-06
Games
One of the great game industry battles of the turn of century was the standoff between Quake III Arena and Unreal Tournament. With both multiplayer focused first person shooters released just weeks apart from one another, that the two games would wind up going head to head was inevitable. If pressed I am always going to have to say I favour the former, but the remarkable thing for us Linux users is that, for a time, both games lived harmoniously under the same publisher. While Quake III Arena was granted its place in eternity when its source code was released in 2005, community support for Unreal Tournament was able to breathe some new life into the game, even with the limitations of the closed binary. Even a strong community can’t fix such problems.
Recently, Motherboard obtained a copy of the contract businesses are required to sign before being admitted to Apple’s IRP Program. The contract, which has not previously been made public, sheds new light on a program Apple initially touted as increasing access to repair but has been remarkably silent on ever since. It contains terms that lawyers and repair advocates described as “onerous” and “crazy”; terms that could give Apple significant control over businesses that choose to participate. Concerningly, the contract is also invasive from a consumer privacy standpoint. In order to join the program, the contract states independent repair shops must agree to unannounced audits and inspections by Apple, which are intended, at least in part, to search for and identify the use of “prohibited” repair parts, which Apple can impose fines for. If they leave the program, Apple reserves the right to continue inspecting repair shops for up to five years after a repair shop leaves the program. Apple also requires repair shops in the program to share information about their customers at Apple’s request, including names, phone numbers, and home addresses. Nobody should be surprised by this. The only reason Apple announced this half-hearted program in the first place is to try and take the wind out of the sails of right to repair legislation, which is being proposed all over the US (and beyond), and the terms of this contract only further confirm that. As for the privacy aspect and Apple wanting all that very private user information – if you still think Apple cares about privacy, you really haven’t been paying attention.
The biggest and boldest move in the Feb. 5 reorg being announced internally today involves the Windows Experience (client) and the hardware teams. Microsoft is going to roll up these two businesses into a single team, known as Windows and Devices — reporting to Chief Product Officer Panos Panay, I’ve confirmed with a person familiar with the changes who asked not to be named. The move takes effect on Feb. 25. This means even tighter integration between the people designing and building Surface devices and the people developing Windows. Panay is the driving force behind the Surface products, and those have been doing relatively well, so it makes sense to allow him to take a stab at the future of Windows.
China’s Xiaomi, Huawei Technologies, Oppo and Vivo are joining forces to create a platform for developers outside China to upload apps onto all of their app stores simultaneously, in a move analysts say is meant to challenge the dominance of Google’s Play store. I’m glad Android is open enough to allow alternative application stores to exist, but whether or not non-Chinese application makers would want to partake in a Chinese state-run application store effort is another issue altogether.
Just another heads up that kernel extensions on macOS will soon stop working. This has been known for a while, but you might not even know you’re using kernel extensions in the first place. System extensions on macOS Catalina (10.15) allow software like network extensions and endpoint security solutions to extend the functionality of macOS without requiring kernel-level access. At WWDC19, we announced the deprecation of kernel extensions as part of our ongoing effort to modernize the platform, improve security and reliability, and enable more user-friendly distribution methods. Kernel programming interfaces (KPIs) will be deprecated as alternatives become available, and future OS releases will no longer load kernel extensions that use deprecated KPIs by default. If you use macOS, run kextstat | grep -v com.apple to see how many third party kernel extensions you have running. Things like VirtualBox, controller support for Steam, DropBox, Little Snitch, and more all come with kernel extensions, so there’s definitely chances you might be running some without even realising it.
I suspect that Wacom doesn’t really think that it’s acceptable to record the name of every application I open on my personal laptop. I suspect that this is why their privacy policy doesn’t really admit that this is what that they do. I imagine that if pressed they would argue that the name of every application I open on my personal laptop falls into one of their broad buckets like “aggregate data” or “technical session information”, although it’s not immediately obvious to me which bucket. Does Wacom have any competitors? Can you even vote with your wallet, or is this yet another market that isn’t really a market at all?
So the Democratic party of Iowa tried to use an untested app to report caucus results during the Iowa primary caucus, and… It went as well as you’d expect. Digging deeper into the app, it should’ve been obvious this was never going to work. In this case, however, it looks like Shadow used a test platform for the app’s public distribution. Installing software through a test platform or sideloading onto your device manually both come with security risks, as app store review processes are designed to discover whether a piece of software is hiding malware or does something behind the scenes it’s not supposed to. In the event you do sideload an app or try installing an unofficial version, your smartphone typically warns you of the risks and asks if you want to proceed. It’s also a less stable model for deploying software at scale, which might explain the difficulty precinct chiefs had in downloading the program. The screenshot from Motherboard also shows that the app was distributed using the platform’s free tier and not its enterprise one. That means Shadow didn’t even pony up for the TestFairy plan that comes with single sign-on authentication, unlimited data retention, and end-to-end encryption. Instead, it looks like the company used the version of TestFairy anyone can try for free, which deletes any app data after 30 days and limits the number of test users that can access the app to 200. What an unmitigated disaster. We’re in 2020 right? Not in 1783?
With Google Takeout, you can download your data from Google apps as a backup or for use with another service. Unfortunately, a brief issue with the tool last November saw your videos in Google Photos possibly get exported to strangers’ archives. How does this even happen? Too bad companies like this have armies of lawyers and obtuse terms of service to hide behind – since software is a special little butterfly that isn’t held to the same standards as any other product we use – so nobody will ever be held accountable for this.
We’re now past Catalina’s midpoint: with four versions already released, there’s only three more to go before we prepare for the first release of 10.16. That’s a stark fact, that we’re now at the point where the more cautious should consider whether they’ll run 10.15. Unusually for macOS, there are many Mac users with Catalina-compatible Macs who are no more able to upgrade now than they were back in October. These include the many who still have to rely on 32-bit apps, and those whose Mac doesn’t start up from an SSD. There’s still a lot of trepidation about Catalina, even among the Apple faithful in popular podcasts like ATP.
The real reason for Britain’s nonexclusion of Huawei was kept under wraps by its government: fear of retaliation. After Brexit, London sees itself as dependent on Beijing’s goodwill. In an interview with the Global Times on Jan. 20, the Chinese ambassador to Britain made it clear that an exclusion of Huawei would severely damage economic and political relations. And for Johnson, the threats from Beijing—a government with expansive control over its national economy—were more credible than those of U.S. President Donald Trump’s administration. Of course, fear isn’t much of an appealing public justification, especially for someone such as Johnson, who wants to project the image of a fearless leader. That’s why the government has come up with an extensive technical justification for the decision—an explanation that’s full of contradictions. Wait, you mean to tell me that going alone instead of being part of the biggest trade and power block after the US opens you up to manipulation and spying by and subservience to the likes of China and Russia? This should make it clear to the US and the EU that the UK should not be trusted with intelligence data.
We’re very grateful to this week’s sponsor: UnitySync®. For a unified GAL and more, UnitySync helps sync objects between LDAP and cloud directories with this highly scalable and customizable tool. Directory Wizards offers responsive technical support before and after your purchase, as well as other directory tools to simplify directory maintenance. A free evaluation available to test drive your solution. Please visit their website to learn more: https://www.dirwiz.com/unitysync .
USB Implementers Forum, the support organization for the advancement and adoption of USB technology, today announced the publication of the USB4 specification, a major update to deliver the next-generation USB architecture that complements and builds upon the existing USB 3.2 and USB 2.0 architectures. The USB4 architecture is based on the Thunderbolt protocol specification recently contributed by Intel Corporation to the USB Promoter Group. It doubles the maximum aggregate bandwidth of USB and enables multiple simultaneous data and display protocols. As the USB Type-C connector has evolved into the role as the external display port of many host products, the USB4 specification provides the host the ability to optimally scale allocations for display data flow. Even as the USB4 specification introduces a new underlying protocol, compatibility with existing USB 3.2, USB 2.0 and Thunderbolt 3 hosts and devices is supported; the resulting connection scales to the best mutual capability of the devices being connected. How many years until USB4 (or later) replaces HDMI and DisplayPort? Since everything is data packets now – analog is a thing of the past – do we really need to have separate video cables? I’d love to one day build a PC that just has an array of USB-C ports on the back, with the ability to plug anything – monitor, keyboard, mouse, serial port adapter for the Windows CE mini laptop I’ve been craving to buy for ages, you know, the usual stuff – into any of the ports. One can dream.
System calls are a way for unprivileged, user applications to request services from the kernel. In the RISC-V architecture, we invoke the call using the ecall instruction. This will cause the CPU to halt what it’s doing, elevate privilege modes, and then jump to whatever function handler is stored in the mtvec (machine trap vector) register. Remember, this is the “funnel” where all traps are handled, including our system calls. We have to set up our convention for handling system calls. We can use a convention that already exists, so we can interface with a library, such as newlib. But, let’s make this ours! We get to say what the system call numbers are, and where they will be when we execute a system call. This is part 7 in a long series about writing a RISC-V operating system in Rust.
EU lawmakers overwhelmingly called on Thursday for rules to establish a common charger for all mobile device makers across Europe, a drive that iPhone maker Apple has criticised. Members of the European Parliament voted by 582-40 for a resolution urging the European Commission, which drafts EU laws, to ensure that EU consumers are no longer obliged to buy new chargers with each new device. This story is a case of government regulation done extremely well. This whole process started with a voluntary agreement in the industry to standardise on one charger and port, and if they failed, the EU would step in and enforce it by law. This agreement has worked out quite well – first micro USB, now USB-C. However, one popular phone maker decided to not adhere to the agreement, and so, more than ten years after the agreement, and thus ample time for this phone maker to follow suit, the EU will now have to step in. Apple has already moved all of its devices to USB-C, save for one – the iPhone. Now they won’t have much of a choice but to follow along. Much like with RoHS, the rest of the world has only benefited from this push for a charging standard, as anyone who remembers the feature phone and PDA days can only attest to (you should see my mutually incompatible collection of just PDA chargers – I must have dozens of them!). And no, this won’t stifle innovation. This whole process is done in collaboration with the industry and standards bodies, so if newer options come along that the sector wants to standardise on, they can – just as they did with the move from micro USB to USB-C. Apple will just have to suck it up – maybe while they’re at it, they can finally make a charging cable that doesn’t suck?
Two-factor security is a basic requirement these days if you want to take your digital responsibilities seriously, but some hardware lacks the sort of public documentation that some privacy advocates feel is truly necessary to provide ideal security. Open source enthusiasts will be glad to hear that Google has just announced the release of OpenSK, an open-source implementation for security keys, supporting both FIDO U2F and FIDO2. I’ve always loved the idea of carrying a small piece of hardware to serve as an authentication device, but I’ve never done any serious research into the concept. Of course, and such system would need to be 100% open source, so maybe OpenSK is a contender.
Under hard time pressure, the ground had to quickly figure out what was wrong and devise a workaround. What they came up with was the most brilliant computer hack of the entire Apollo program, and possibly in the entire history of electronic computing. To explain exactly what the hack was, how it functioned, and the issues facing the developers during its creation, we need to dig deep into how the Apollo Guidance Computer worked. Hold onto your hats, Ars readers—we’re going in. Amazing story.
IBM named Arvind Krishna as chief executive officer, replacing longtime CEO Virginia Rometty. Krishna is currently the head of IBM’s cloud and cognitive software unit and was a principal architect of the company’s purchase of Red Hat, which was completed last year. Rometty, 62, will continue as executive chairman and serve through the end of the year, when she will retire after almost 40 years with the company, IBM said in a statement Thursday. Good luck to the man, I guess. IBM isn’t exactly the most exciting company in the world.
Today, I watched a SpaceX Falcon 9 rocket leave Cape Canaveral and deliver 60 small Starlink satellites to Low Earth Orbit (LEO) on the Starlink L3 mission. For those not with us last week, SpaceX has a subsidiary, known as Starlink, which is presently endeavoring to blanket the majority of the inhabited latitudes of Earth with orbiting satellites to provide wireless internet access and private-line communications services. This is a Big Deal, the consequences of which I will explain momentarily. But first, some background. Out of all of Elon Musk’s crazy projects, this is the only one that interests me. This project can have huge consequences.
The iPad is now ten years old, and people still have to write articles about how, no, really, you can do real work on an iPad! In 1994, ten years after the Mac was originally introduced, I got my first computer, a Performa 450. Nobody wrote any articles about how, actually, real work on a Mac is possible. Everybody who had a Mac used it for real work. There was no need to write articles about how you could use Macs for real work, because for Macs, it was – and still is – actually true. There are countless people who work on iPads, but the central thread in almost all of the articles and stories about these people is that they involve countless, extensive compromises to make it work – whether that’s resorting to a PC for a lot of tasks, or using complex, hacky Shortcuts to accomplish things any other computer can do without you even thinking about it. I see no reason an iPad can’t be a full, proper computer that can replace many a laptop and desktop, but Apple will need to put some serious weight behind iOS as a platform. The hardware is more than capable – it’s the software that holds it back. The fact we’re ten years into this thing and there’s still no Xcode for iPad tells you all you need to know about how Apple sees the iPad.
Submitted by