Debian/Trixie now "stable"
Very disappointed to see Trixie become the new stable release. Some
apparent changes, like moving to systemd networking, just aren't ready.
I noticed this immediately when trying to upgrade a headless server over
ssh. It somehow decided that my network IP settings needed to be /32
instead of /24, resulting in it becoming disconnected from the network.
This crashed the ssh session and left the server mid-configuration.
After I attached it to a keyboard and monitor I was able to complete the
configuration from a rescue session. However the machine was still
unavailable until I realized that the network mask was wrong.
So now I can reach the machine but systemd networking still delivers
miserable performance compared to the far more mature network manager.
There is something fundamentally messed up with how it handles both
bridging and bonding. Fortunately my servers don't connect via wifi or
I'd be in even more trouble.
Only one of my VMs started because libvirt clobbered a symlink to my VM
images folder that I use rather than manually editing the image location
for each file.
I'm still trying to figure out what changed to take down my nextcloud
server and has made my jitsi server unusable.
And this is before looking at Wayland for desktop-centric machines.
I have been using Debian for decades and have come to expect that new
releases will not only not suffer from crashes, but will also work well.
I recognize that maintaining both network manager and systemd networking
(and X11 and Wayland) is difficult, but perhaps we should be waiting
until the newer technology reaches a mature enough state that it
actually can match what the existing technology does.
Reply to: