Re: Debian/Trixie now "stable"
On 8/10/25 23:10, Gary Dale wrote:
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,
Look at the logs to see what went rong.
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.
I've been using systemd-networkd for years now without issues including
bridges and bounding.
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.
How is this related to the networking stak?
Were files in '/etc/system/networkd' auto-generated?
I have upgraded and fresh installed Trixie servers without a switch to
systemd-networkd.
--
John Doe
Reply to: