- wlug - list.wlug.org.nz

Intel Kills Its RISC-V Development Environment
by Lawrence D'Oliveiro 30 Jan '23

30 Jan '23

Intel is abandoning its “Pathfinder” project <https://www.theregister.com/2023/01/30/intel_ris_v_pathfinder_discontinued/> which was an integrated environment for doing development targeted at RISC-V processors. What does this mean for RISC-V? Not a lot, I would say. What does it mean for Intel? I think the basic problem here is the same as with its attempts to move into ARM: you have a high-volume, low-margin business where a company that has grown fat on not-so-high-volume, quite high-margin x86 processors was never going to be able to compete.

1 0

Jeremy Allison Laid Off From Google
by Lawrence D'Oliveiro 28 Jan '23

28 Jan '23

Seems the latest round of layoffs from Google has hit its open-source projects particularly hard, according to Steven J Vaughan-Nichols <https://www.theregister.com/2023/01/27/google_open_source/>. The one name that immediately caught my eye was Jeremy Allison, one of the chief brains behind Samba <https://www.samba.org/>. Before joining Google, he worked at Novell. He left there in 2006 because he objected to a deal Novell made with Microsoft which was effectively a patent licence for Free software (something which the GPL doesn’t allow) <https://www.zdnet.com/article/in-case-you-missed-it-part-1-jeremy-allison-f…>. While waiting to see where else he turns up, it is worth revisiting this essay <https://www.samba.org/samba/news/articles/low_point/tale_two_stds_os2.html> from shortly before that time, where he does a comparison between the Microsoft Windows and POSIX APIs, and why there can be so many independent, yet interoperable implementations of the latter, and why there can be only one of the former (though the WINE project continues to try to change that).

1 0

Consumer Reports Looks At Memory Safety
by Lawrence D'Oliveiro 27 Jan '23

27 Jan '23

The nonprofit Consumer Reports foundation has done a study of, of all things, memory safety in computer software <https://www.theregister.com/2023/01/26/memory_safety_mainstream/>. It apparently came to the need for this after putting together a consumer-focused guide to online security. Seems like greater adoption of the Rust programming language is becoming a key part of improving the situation. Asked about C++ creator Bjarne Stroustrup's assertion that ISO standard C++ can be memory safe when rules are enforced with static analysis, [Josh Aas, of the nonprofit Internet Security Research Group] expressed skepticism. "In a very theoretical sense that ignores the practicalities of the real world, that might be true," he said. "It might very theoretically be practically possible to write memory safe C++. But it's just not how things work in our world. There are just better ways to do that. C++ was not designed from the ground up to offer memory safety."

1 0

Android 14 Set To Block Certain Outdated Apps From Being Installed
by Peter Reutemann 25 Jan '23

25 Jan '23

'To help reduce the potential for malware, Android 14 will begin fully blocking the installation of apps that target outdated versions of Android. 9to5Google reports: For years now, the guidelines for the Google Play Store have ensured that Android developers keep their apps updated to use the latest features and safety measures of the Android platform. Just this month, the guidelines were updated, requiring newly listed Play Store apps to target Android 12 at a minimum. Up to this point, these minimum API level requirements have only applied to apps that are intended for the Google Play Store. Should a developer wish to create an app for an older version, they can do so and simply ask their users to sideload the APK file manually. Similarly, if an Android app hasn't been updated since the guidelines changed, the Play Store will continue serving the app to those who have installed it once before. According to a newly posted code change, Android 14 is set to make API requirements stricter, entirely blocking the installation of outdated apps. This change would block users from sideloading specific APK files and also block app stores from installing those same apps. Initially, Android 14 devices will only block apps that target especially old Android versions. Over time though, the plan is to increase the threshold to Android 6.0 (Marshmallow), with Google having a mechanism to "progressively ramp [it] up." That said, it will likely still be up to each device maker to decide the threshold for outdated apps or whether to enable it at all. The report notes that it'll still be possible to install an outdated version of an app "through a command shell, by using a new flag."' -- source: https://tech.slashdot.org/story/23/01/24/225226 Cheers, Peter -- Peter Reutemann Dept. of Computer Science University of Waikato, Hamilton, NZ Mobile +64 22 190 2375 https://www.cs.waikato.ac.nz/~fracpete/ http://www.data-mining.co.nz/

1 0

Google’s Fuchsia OS was one of the hardest hit by last week’s layoffs
by Peter Reutemann 24 Jan '23

24 Jan '23

'Google is still reeling from the biggest layoff in company history last Friday. Earlier cost cuts over the past six months have resulted in several projects being shut down or deprioritized at Google, and it's hard to fire 12,000 people without some additional projects taking a hit. The New York Times has a report about which divisions are being hit the hardest, and a big one is Google's future OS development group, Fuchsia. While the overall company cut 6 percent of its employees, the Times pointed out that Fuchsia saw an outsize 16 percent of the 400-person staff take a hit. While it's not clear what that means for the future of the division, the future of Fuchsia's division has never really been clear. Fuchsia has been a continuous mystery inside Google since it first saw widespread press coverage in 2017. Google rarely officially talks about it, leaving mostly rumors and Github documentation for figuring out what's going on. The OS isn't a small project, though—it's not even based on Linux, opting instead to use a custom, in-house kernel, so Google really is building an entire OS from scratch. Google actually ships the OS today to consumers in its Nest smart displays, where it replaced the older Cast OS. The in-place operating system swap was completely invisible to consumers compared to the old OS, came with zero benefits, and was never officially announced or promoted. There's not much you can do with it on a locked-down smart display, so even after shipping, Fuchsia is still a mystery. The biggest questions surrounding Fuchsia are: "Why does this exist, and what are its goals?" Is Fuchsia an eventual replacement for Android or Chrome OS? Around 2018, when we first got Fuchsia running on a Pixelbook, the source code documentation for the custom kernel said it "targets modern phones and modern personal computers with fast processors," which certainly made it sound like an Android and/or Chrome OS successor being built for flagship devices. That early codebase also included graphical user interfaces for PCs and phones, further driving home that this was a consumer OS. After Fuchsia got some initial publicity, it removed its public interface code. 2018 also saw a foundational Bloomberg report calling Fuchsia "a successor to Android," and saying the team planned to launch on smart speakers in 2021 (which was spot on) and would later move into phones and laptops in 2023. Even the name "Fuchsia" was a reference to Apple projects some members of the team had been involved with. "Pink" was the codename for a canceled successor to classic Mac OS, and "Purple" was the codename for the iPhone OS. The color Fuchsia is a mix of pink and purple, so this all sounded very ambitious.' -- source: https://arstechnica.com/gadgets/2023/01/big-layoffs-at-googles-fuchsia-os-c… Cheers, Peter -- Peter Reutemann Dept. of Computer Science University of Waikato, Hamilton, NZ Mobile +64 22 190 2375 https://www.cs.waikato.ac.nz/~fracpete/ http://www.data-mining.co.nz/

2 1

83% of GNOME Users Installed Extensions, Survey Shows
by Peter Reutemann 24 Jan '23

24 Jan '23

'Last summer GNOME invited people to voluntarily run the tool gnome-info-collect on their systems to send back (non-sensitive/non-identifiable) data about their system configurations. 2,560 people ran the tool, and they're now releasing the data. Here's the distribution of distros for all 2,560 respondents: Fedora: 1,376 (54.69%) Arch: 469 (18.64%) Ubuntu: 267 (10.61%) Manjaro: 140 (5.56%) EndeavourOS: 66 (2.62%) Debian: 44 (1.75%) openSUSE: 38 (1.51%) Pop! 38 (1.51%) Other: 78 (3.10%) And the breakdown of hardware manufacturers (top four): Lenovo: 516 (23.54%) Dell: 329 (15.01%) ASUS: 261 (11.91%) HP: 223 (10.17%) The site OMG! Linux pointed out that 90% of systems had Flatpak installed — (though it's enabled by default on Fedora, which was 54.69% of all the respondents). Some other interesting stats they noticed: - Most common default browser: Firefox (73.14%), Chrome (11.64%), Brave (4.76%). [Microsoft Edge was the default browser on 37 systems (1.51%) ] - 83% of users have at least one (non-default) GNOME extension installed - 'App Indicator' is the most popular extension (by 43% of those using extensions) - GSConnect, User Themes, and Dash to Panel/Dock also widely used - Most popular desktop apps: GIMP (58.48%), VLC (53.71%), Steam (53.40%) [...] The popularity of GNOME extensions will surprise no-one. It is a solid indicator that the existing GNOME extension system is good at doing what it's there to: let users augment and extend their system in the ways they want. GNOME's report adds that "it's exciting to see the popularity of new GNOME apps like Flatseal, To Do, Bottles, and Fragments." One other interesting stat from their report: 55% of the participants were using Online Accounts, with Google the most common one added, followed by Nextcloud and Microsoft. But "Some of the account types had very little usage at all, with Foursquare, Facebook, Media Server, Flickr and Last.fm all being active on less than 1% of systems."' -- source: https://tech.slashdot.org/story/23/01/23/0355247 Cheers, Peter -- Peter Reutemann Dept. of Computer Science University of Waikato, Hamilton, NZ Mobile +64 22 190 2375 https://www.cs.waikato.ac.nz/~fracpete/ http://www.data-mining.co.nz/

1 0

Which Performs Better on Linux: Firefox or Chrome?
by Peter Reutemann 23 Jan '23

23 Jan '23

'Phoronix compares the performance of Firefox and Chrome on the Linux desktop. They used recent releases (at default settings) for both browsers on an Intel Core i9 13900K "Raptor Lake" system with Radeon RX 6700XT graphics, concluding "out-of-the-box Google Chrome continues performing much better overall than Mozilla Firefox." One area where Firefox does better out-of-the-box is around the HTML5 Canvas such as measured via the CanvasMark test case. For the demanding JetStream 2 benchmark as one of the most demanding browser tests currently, Chrome on Linux was 67% faster than Firefox on this same Intel Raptor Lake desktop. Firefox did have a small win in the rather basic JavaScript Maze solver benchmark. Firefox at least was in a competitive space for the WebAssembly (WASM) benchmarks, but aside from that Google Chrome continues holding strong on Linux in the performance department.' -- source: https://news.slashdot.org/story/23/01/22/1922212 Cheers, Peter -- Peter Reutemann Dept. of Computer Science University of Waikato, Hamilton, NZ Mobile +64 22 190 2375 https://www.cs.waikato.ac.nz/~fracpete/ http://www.data-mining.co.nz/

1 0

Pioneering Apple Lisa goes “open source” thanks to Computer History Museum
by Peter Reutemann 20 Jan '23

20 Jan '23

'As part of the Apple Lisa's 40th birthday celebrations, the Computer History Museum has released the source code for Lisa OS version 3.1 under an Apple Academic License Agreement. With Apple's blessing, the Pascal source code is available for download from the CHM website after filling out a form. Lisa Office System 3.1 dates back to April 1984, during the early Mac era, and it was the Lisa equivalent of operating systems like macOS and Windows today. The entire source package weighs is about 26MB and consists of over 1,300 commented source files, divided nicely into subfolders that denote code for the main Lisa OS, various included apps, and the Lisa Toolkit development system.' -- source: https://arstechnica.com/information-technology/2023/01/pioneering-apple-lis… Cheers, Peter -- Peter Reutemann Dept. of Computer Science University of Waikato, Hamilton, NZ Mobile +64 22 190 2375 https://www.cs.waikato.ac.nz/~fracpete/ http://www.data-mining.co.nz/

2 1

How Amazon Scammers Get Good Product Reviews
by Lawrence D'Oliveiro 18 Jan '23

18 Jan '23

In this report on a fake <https://arstechnica.com/gadgets/2023/01/64gb-microsd-cards-are-posing-as-16…> 16TB SSD that only turned out to be 64GB, there is a description of how the seller was able to accumulate quite a bunch of effusive reviews: the listing would originally have been for an entirely different, legitimate product. Then once a good number of positive comments had been built up, it would have been switched for the scam. The switch might happen multiple times, for legitimate products each time, to keep adding to the positivity, until the final con. However, this does mean that you end up with an accumulation of rather odd reviews: However, reading some of these reviews made me question if we've been using SSDs wrong all this time. A review on one of the remarkably cheap portable SSD listings declared the product to be "a very colorful throw, but thinner" than expected. Another reported that the drive proved "very soft and perfect" for their 6-year-old. One review pointed to the SSD being a "beautiful portrait" that looks great in the kitchen, while another five-star review pointed to the high microphone and video quality.

1 0

MSI Accidentally Breaks Secure Boot for Hundreds of Motherboards
by Peter Reutemann 18 Jan '23

18 Jan '23

'Over 290 MSI motherboards are reportedly affected by an insecure default UEFI Secure Boot setting that allows any operating system image to run regardless of whether it has a wrong or missing signature. From a report: This discovery comes from a Polish security researcher named Dawid Potocki, who claims that he did not receive a response despite his efforts to contact MSI and inform them about the issue. The issue, according to Potocki, impacts many Intel and AMD-based MSI motherboards that use a recent firmware version, affecting even brand-new MSI motherboard models.' -- source: https://tech.slashdot.org/story/23/01/17/1728239 Cheers, Peter -- Peter Reutemann Dept. of Computer Science University of Waikato, Hamilton, NZ Mobile +64 22 190 2375 https://www.cs.waikato.ac.nz/~fracpete/ http://www.data-mining.co.nz/

1 0