New features in 23.10 Updated Packages
add-apt-repository now adds PPAs as deb822 .sources files (Improvements to PPA management in 23.10 116).
Linux kernel :penguin:
Ubuntu 23.10 includes the new 6.5 Linux kernel that brings many new features.
Notable upstream changes:
Intel’s “Topology Aware Register and PM Capsule Interface” (interface that provides better power-management features).
arm64 permission-indirection extension (technology to set special memory permissions).
RISC-V now supports ACPI.
The Loongarch architecture now supports simultaneous multi-threading (SMT).
Support for unaccepted memory (protocol by which secure guest systems accept memory allocated by the host - Seeking an acceptable unaccepted memory policy 5.
The io_uring subsystem can now store the rings and submission queue in user-space memory.
Ability to mount a file system underneath an existing mount on the same mount point; useful in container scenarios (Merge tag ‘v6.5/vfs.mount’ of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs 5).
New cachestat() system call (query the page-cache state of files and directories).
Usual set of changes to support new hardware.
Notable Ubuntu-specific changes:
zstd compressed modules (LP: #2028568 11) to shorten boot time.
New Apparmor/Stacking LSM patch set.
Updated shiftfs patch set.
Enabled multi-gen LRU page reclaiming by default (LP: #2023629 1).
.config tuning of the low-latency kernel for desktop-oriented tasks (LP: #2028568 6).
New zfs 2.2.0~rc3.
Ceph support for idmapped mounts.
systemd v253.5
The init system was updated to systemd v253.5. See the upstream changelog 6 for more information about individual features. Netplan v0.107
The network stack was updated to Netplan v0.107 3, introducing support for dummy and veth devices in addition to providing Python bindings to libnetplan in the python3-netplan package. Toolchain Upgrades :hammer_and_wrench:
GCC was updated to the 13.2.0 release, binutils to 2.41, and glibc to 2.38.
Python :snake: now defaults to version 3.11.6, and 3.12.0 is available in the archive.
Perl :camel: at version 5.36.0.
LLVM now defaults to version 16, and 17 is available in the archive.
Rust :crab: toolchain defaults to version 1.71.
Thanks but no thanks. I’ll stay with my debian unstable: less snap bullshit, no advertising in motd and newer packages (systemd 254 for example)
who said debian uses old packages again?
I’m about to jump from Ubuntu back to good ol’ Debian. I was planning on testing, but I’ve heard a few times recently that people are running unstable for day-to-day desktop use. Is there any particular reason you went with unstable instead of testing? Any issues so far?
most of the time it works every time. :)
I’m using debian unstable as a desktop OS on all of my 3 regularly used systems: 2 notebooks and 1 desktop. And debian 11 on citrix virtual desktop at work. debian stable on around 200 servers.
I rarely have bigger issues in my day to day usage of unstable which includes surfing, gaming and coding. at the moment my bluetooth headset microphone doesn’t work, which i guess is due to some changes to pipewire but only on my desktop. both my work and private notebook seem to not have issues.
this is one of the worst problems i had in the last 8 years. other then that, if you use apt-listbugs to exclude any updates with serious bugs by pinning them until a bugfree version gets released, you wont have any more issues then you get with arch for example.
For one thing, both Unstable and Stable are quicker to get security fixes than Testing.
You can integrate
debsecanwithaptand pull security updates fromexperimentalandunstableas recommended in the wiki.Hey, I like my old packages. Debian LTS is great for servers. I’m won’t even need to think about updates for years.
Me too. Stable packages, unlike everyone thinks, doesn’t mean it is bug free, it means that the software versions don’t change. And that exactly lets me enable unattended-upgrades and forget about the server for years, without risking to fubar the system because of some config changes or new options