Canonical Releases Ubuntu 22.10 Kinetic Kudu

Canonical blog: Codenamed "Kinetic Kudu," this interim release improves the experience of enterprise developers and IT administrators. It also includes the latest toolchains and applications with a particular focus on the IoT ecosystem. Ubuntu 22.10 delivers toolchain updates to Ruby, Go, GCC and Rust. OpenSSH in Ubuntu 22.10 is configured by default to use systemd socket activation, meaning that sshd will not be started until an incoming connection request is received. This reduces the memory footprint of Ubuntu Server on smaller devices, VMs or LXD containers. Ubuntu 22.10 also comes with a new debuginfod service to help developers and admins debug programs shipped with Ubuntu. Debugging tools like gdb will automatically download the required debug symbols over HTTPS.

Ubuntu 22.10 now supports MicroPython on a variety of microcontrollers, including the Raspberry Pi Pico W. rshell, thonny and mpremote are all available in the Ubuntu repositories. The Ubuntu graphics stack transition to kms means developers can run Pi-based graphical applications using frameworks like Qt outside of a desktop session and without Pi specific drivers. This complements expanded support for a range of embedded displays for the Raspberry Pi, including the Inky eInk HAT series, Hyperpixel range and the Raspberry Pi Official Touchscreen. [...] All users will benefit from the refinements in GNOME 43, including GTK4 theming for improved performance and consistency. Quick Settings now provide faster access to commonly used options such as wifi, bluetooth, dark mode and power settings.

systemd socket activation? Really?

[Entrope]

Why couldn't the Cult Of Lennart just admit that they have reinvented inetd (probably poorly, with apologies to Henry Spencer)?

Re:systemd socket activation? Really?

[fahrbot-bot]

YAS"S" -- Yet Another Systemd "Service"

[ Pretty soon Emacs and Systemd will have duke it out for the kitchen sink -- my money's on Emacs. :-) ]

(Quipped as a *long* time Emacs user.)

Re:

[Gavagai80]

They do admit they're reinventing things, sometimes just copy-pasting them. The point of systemd is to ensure that the tool will be available and accessible in a standard way across all distributions that use systemd. That's why the people who spend their days worrying about software compatibility and dependencies (the distro makers) love it and force it on everyone.

Re:

[fahrbot-bot]

The point of systemd is to ensure that the tool will be available and accessible in a standard way across all distributions that use systemd.

That's a nice, and maybe a little naive, way to put it. I'd feel better if (a) it wasn't horrendously "designed" and trying to do *everything*, especially things it doesn't need to do, and often not optimally; (b) that it had a multi-vendor standards body overseeing its development rather than being pushed by Red Hat; (c) wasn't another "quality" piece of software from Lennart [see (a)] and (d) didn't run as PID 1, with, instead, a smaller, simpler, more focused process in that role. But that's just MHO .

Re:

[tlhIngan]

That's a nice, and maybe a little naive, way to put it. I'd feel better if (a) it wasn't horrendously "designed" and trying to do *everything*, especially things it doesn't need to do, and often not optimally; (b) that it had a multi-vendor standards body overseeing its development rather than being pushed by Red Hat; (c) wasn't another "quality" piece of software from Lennart [see (a)] and (d) didn't run as PID 1, with, instead, a smaller, simpler, more focused process in that role. But that's just MHO ...

Re:

[fahrbot-bot]

Well laid out, thanks.

... or to do all those things systemd does, ...

I imagine many would prefer it do less (and/or fewer) -- and do those better.
I mean, does systemd really need to do DNS, or NTP or NFS -- etc ... ? Pretty sure the answer is no.

Re:

[Entrope]

You never used inetd, did you? It was dead simple to configure. Exactly what do you think was inconsistent across distros with it?

Uh-oh

[Trip Ericson]

"OpenSSH in Ubuntu 22.10 is configured by default to use systemd socket activation, meaning that sshd will not be started until an incoming connection request is received."

So I should expect that ssh will not work properly when I eventually get this functionality in 24.04? Is there nothing that systemd won't absorb and destroy?

Re:

[93 Escort Wagon]

Speaking as someone who has to admin several dozen AlmaLinux / CentOS machines - it seems that, with every iteration of systemd, the time I'm forced to waste dealing with basic system services increases.

systemd is oriented toward linux on the desktop

[Behrooz]

systemd is oriented toward linux on the desktop and starting up quickly... which nearly nobody who actually does things cares about.

I could not give fewer shits about starting up a headless server quickly, but it irritates the living fuck out of me when systemd does something like just GIVING UP on mounting a flaky nfs share (from an admittedly shitty appliance, which my services are constrained to use regardless) one time in ten because network services aren't really ready yet, or the first attempt timed o

Re:

[ArchieBunker]

What the fuck is the point of that?

Anyone using the KDE spin of Fedora?

[Tailhook]

Wondering what your experience is.

Re:

[Junta]

I used to use KDE under Ubuntu and will say the KDE spin of Fedora is mostly better executed.

I did have to switch back to X11, because too many things are glitchy in Wayland, particularly Plasma shell.

As a user of bluetooth headset, the more competent use of pipewire is nice.

The fact that Ubuntu snapifies everything drove me over to Fedora, where flatpak is as close as it gets and you have to opt-in to flathub, otherwise Fedora packaging pretty much ignores that and packages everything up in a nice and trad

Re:

[Tailhook]

The fact that Ubuntu snapifies everything drove me over to Fedora

That's why I'm looking to switch.

The biggest pain is the strict avoidance of any vaguely non-open content.

If it's a choice between working around that and dealing with snap I'll take the former.

Can they fix the stupid Snap message?

[Tim the Gecko]

There's an annoying "Pending update of "firefox" snap. Close the app to avoid disruptions" message that pops up every few days. It doesn't tell you how long to close Firefox for, or how to make the update happen, how you might tell if you can open it again, or anything useful. You just have to find the answer [askubuntu.com] yourself. I'm surprised this has been going on so long without any improvement.

Re:Can they fix the stupid Snap message?

[Trip Ericson]

Better solution is to just remove the Firefox Snap and replace it with the Firefox .deb. Or, take it a step further like I did and tear out snapd completely and blacklist it.

Re:Can they fix the stupid Snap message?

[ArchieBunker]

Just uninstall snap. It used to piss me off some much occasionally needing to run the default calculator program. Hit the windows key, type in calc and press enter. Wait a few seconds for it to load. Meanwhile xcalc loads instantaneously.

Re: Can they fix the stupid Snap message?

[Anonymouse Cowtard]

snap refresh

Re:

[u53r]

All you have to do is close Firefox first then snap refresh

Quick

[ArchieBunker]

Set a static ip address from the command line without googling. Tell me how you fare.

Re:

[iggymanz]

easy, I just keep using /etc/network/interfaces for permanent configuration and ifconfig(8) for temp and not that netplan or networkmanager faggot shit.

There are those who would love to hold meeting with the inventor of these new extraneous alternate ways of network config, and also of systemd, in a dark alley along with the guest of honor, a lead pipe.

Linux should develop one distro...

[Hey_Jude_Jesus]

for anyone to install & use. What if there were 25 distros of Microsoft Windows? We can sell computers with one distro that people can use just like Mac & Intel computers. IMHO & YMMV

Re:

[Anonymouse Cowtard]

Fine. Which distro and how will you force everyone else to accept your choice?