Ubuntu has put out the latest point release of its stable version, or the fourth bugfix of 20.04. The main difference will be visible in new installs: a clean install of 20.04.4 – for example on some new hardware – will get kernel version 5.13 from 21.10 "Impish Indri", which came out after 20.04.3 last August. However, if …
I'd just recently had to do a reinstall on my home laptop. [Long story that I might share more about once correspondence ends.] Anyway, I was having just this problem, with nVidia drivers, and was a little confused what had changed. I'd been working around the issue by booting to the earlier kernel but it's good to get more information about it.
Thanks Reg. :-)
My car's SatNav needs a major update - it's constantly in the Grand Canal in Venice (£150), the screen wash is gone, oil & filter needs changing and the engine flushing. It never fully recovered from me accidentally putting diesel into the petrol tank. Sump plug leaks. Plus the tyres are half flat as they've perished. Wipers are split and the driver's side mirror is taped on. It has no 2nd gear.
God how I wish I could just go online and update the damn car...
P.S. Before anyone says it, I don't mean via webuyanycar.com. I'm attached to Henry.
This reminds me, this autumn I'll have to roll my 18.04.5 systems up to 22.04.1
If I remember rightly, when I went from 14.04 to 18.04 I found it easiest to bounce through 16.04.
Still way less hassle than a Windows upgrade (what do you mean, you want sound AND better than 800x600 screen resolution?)
The only problem with the 'free' Ubuntu Essential Subscription is that you have to prove that you've done things to aid the Ubuntu community, like taking an active part in the community forums.
I'm a Ubuntu user of 15 years (first install was Dapper Drake). In the past, I pointed people at Ubuntu as a good distro. to move to from other operating systems, but I've never really done anything measurable to aid the community, so I can't get it.
I'm running NVidia driver for my GTX650 at home, and 5.13 kernel. Do make sure to see what precautions they have especially if you did anything custom with your nvidia driver install. But I'm running the regular nvidia-driver Ubuntu package, and have run HWE kernels fore quite a while. I'm running 5.13.0-30 now and update is trouble-free, part of the update process (DKMS) automatically builds the nvidia kernel modules whenever a new kernel is installed, and the nvidia-drivers Ubuntu package has supported 5.13 kernels for quite a while.
I put 20.04 on my Dell Precision tower and have had multiple breakages caused by updates.
I mean I naively installed linux-image-extra (or something) to get a driver for my Wifi card, and clicked something in the gui to get an NVidia driver, thinking that once it was working, it would stay working. But no.
So it turns out the image-extra metapackage only gets you extras for the currently installed Kernel, another one comes along and boom the Wifi driver is gone. Then you can't get on line to Google the problem. So this it turns out is because I needed to install 20.04-hwe which then gets you the "extras" on every update.
But potentially breaks the NVidia driver. Usually in a way in which you can't boot. Or was it something else that caused that? I don't know, I got mightily confused trying to trouble shoot. Lucky it keeps the old Kernel eh? Usually a few days later another update comes along and fixes it, but once (and I don't know if it was me) but I got in a complete mess with it altogether and had to remove everything to do with NVidia then work out which version (of many) actually was required for the current Kernel.
Remember Ubuntu's philosophy used to be "it should just work"?
Some of this is not Canonical's fault. If you choose the Nvidia binary driver, you will find that Nvidia drop support for older cards periodically. If yo have something older than a gtx7xx card there is a good chance that support may be dropped shortly.
If you put the current open-source driver on (nouveau) driver on, it will probably do most of what you want, for cards going back 15 years or so. But doing that from the command line can be a bit tricky.
Canonical's Linux distro for edge devices and the Internet of Things, Ubuntu Core 22, is out.
This is the fourth release of Ubuntu Core, and as you might guess from the version number, it's based on the current Long Term Support release of Ubuntu, version 22.04.
Ubuntu Core is quite a different product from normal Ubuntu, even the text-only Ubuntu Server. Core has no conventional package manager, just Snap, and the OS itself is built from Snap packages. Snap installations and updates are transactional: this means that either they succeed completely, or the OS automatically rolls them back, leaving no trace except an entry in a log file.
The UBPorts community is in the final stages of preparing its next release and it's calling for testers.
Many of them are a few years old now, so there's a good chance that you've already replaced them and they sit unloved and neglected in a drawer. The starred entries in the list of devices are the best supported and should have no show-stopping problems. In order of seniority, that means: the LG-made Google Nexus 5 (2013); the original Oneplus One (2014); two models of Sony Xperia X, the F5121 and F5122 (2016); and Google's Pixel 3a and 3a XL (2019).
At The Linux Foundation's Open Source Summit in Austin, Texas on Tuesday, Linus Torvalds said he expects support for Rust code in the Linux kernel to be merged soon, possibly with the next release, 5.20.
At least since last December, when a patch added support for Rust as a second language for kernel code, the Linux community has been anticipating this transition, in the hope it leads to greater stability and security.
In a conversation with Dirk Hohndel, chief open source officer at Cardano, Torvalds said the patches to integrate Rust have not yet been merged because there's far more caution among Linux kernel maintainers than there was 30 years ago.
Microsoft is flagging up a security hole in its Service Fabric technology when using containerized Linux workloads, and urged customers to upgrade their clusters to the most recent release.
The flaw is tracked as CVE-2022-30137, an elevation-of-privilege vulnerability in Microsoft's Service Fabric. An attacker would need read/write access to the cluster as well as the ability to execute code within a Linux container granted access to the Service Fabric runtime in order to wreak havoc.
Through a compromised container, for instance, a miscreant could gain control of the resource's host Service Fabric node and potentially the entire cluster.
Microsoft has made it official. Windows Subsystem for Linux 2 distributions are now supported on Windows Server 2022.
The technology emerged in preview form last month and represented somewhat of an about-face from the Windows giant, whose employees had previously complained that while the tech was handy for desktop users, sticking it on a server might mean it gets used for things for which it wasn't intended.
(And Windows Server absolutely had to have the bloated user interface of its desktop stablemate as well, right?)
EndeavourOS is a rolling-release Linux distro based on Arch Linux. Although the project is relatively new, having started in 2019, it's the successor to an earlier Arch-based distro called Antergos, so it's not quite as immature as its youth might imply. It's a little more vanilla than Antergos was – for instance, it uses the Calamares cross-distro installer.
EndeavourOS hews more closely to its parent distro than, for example, Manjaro, which we looked at very recently. Unlike Manjaro, it doesn't have its own staging repositories or releases. It installs packages directly from the upstream Arch repositories, using the standard Arch package manager
pacman. It also bundles yay to easily fetch packages from the Arch User Repository, AUR. The
yay command takes the same switches as
pacman does, so if you wanted to install, say, Google Chrome, it's as simple as
yay -s google-chrome and a few seconds later, it's done.
Version 21.3 of Manjaro - codenamed "Ruah" - is here, with kernel 5.15, but don't let its beginner-friendly billing fool you: you will need a clue with this one.
Manjaro Linux is one of the more popular Arch Linux derivatives, and the new version 21.3 is the latest update to version 21, released in 2021. There are three official variants, with GNOME 42.2, KDE 5.24.5 or Xfce 4.16 desktops, plus community builds with Budgie, Cinnamon, MATE, a choice of tiling window managers (i3 or Sway), plus a Docker image.
The Reg took its latest look at Arch Linux a few months ago. Arch is one of the older rolling-release distros, and it's also famously rather minimal. The installation process isn't trivial: it's driven from the command line, and the user does a lot of the hard work, manually partitioning disks and so on.
Old-school editor fans, rejoice: some two and a half years after version 8.2, Vim 9 is here, and with a much faster scripting language.
The existing scripting language, Vimscript, remains and will still work. Only scripts beginning with the line
vim9script will be handled differently. The syntax changes are relatively modest; the important differences are in things like local versus global variables and functions, and that functions defined with
:def will be compiled before they are run. This allows many errors to be caught in advance, but more significantly, compiled functions execute from 10× to 1000× faster.
A bunch of almost unbelievably clever tech tricks come together into something practical with redbean 2: a webserver plus content in a single file that runs on any x86-64 operating system.
The project is the culmination – so far – of a series of remarkable, inspired hacks by programmer Justine Tunney: αcτµαlly pδrταblε εxεcµταblε, Cosmopolitan libc, and the original redbean. It may take a little time to explain what it does, so bear with us. We promise, you will be impressed.
To begin with, redbean uses a remarkable hack known as APE, which stands for Actually Portable Executable – which its author styles αcτµαlly pδrταblε εxεcµταblε. (If you know the Greek alphabet, this reads as "actmally pdrtable execmtable", but hey, it looks cool.)
Analysis Toxic discussions on open-source GitHub projects tend to involve entitlement, subtle insults, and arrogance, according to an academic study. That contrasts with the toxic behavior – typically bad language, hate speech, and harassment – found on other corners of the web.
Whether that seems obvious or not, it's an interesting point to consider because, for one thing, it means technical and non-technical methods to detect and curb toxic behavior on one part of the internet may not therefore work well on GitHub, and if you're involved in communities on the code-hosting giant, you may find this research useful in combating trolls and unacceptable conduct.
It may also mean systems intended to automatically detect and report toxicity in open-source projects, or at least ones on GitHub, may need to be developed specifically for that task due to their unique nature.
Biting the hand that feeds IT © 1998–2022