Live data from Hacker News

What to expect from Debian/Trixie

michael-prokop.at

151–160 of 211 posts

Re: What to expect from Debian/Trixie

#151
post #30

Earlier quoted context omitted.

You might like snapshot based solutions like Snapper

I once tried Spiral Linux, light fork of Sid with bundled Snapper stack. Switched to a giant-userbase distro, Fedora, mostly because Plasma was bad with 5k screens. Are there mainstream distros with easy rollback?

openSUSE should be one of them.

Re: What to expect from Debian/Trixie

#152
Debian has two long running bugs

When you su to root, the whole path or a different path is loaded. One has to type su and then su - in order to reach all the regular bin and abin directories. It is flagged, but Debian team won't fix. As a user it is not great.

Secondly, Debian now ships with Raspberrypifirmware package, even on intel installs. When you enable backports to install a newer kernel, this fails due to this package bring there . It ks a major hassle to fix, and without Chatgpt/competitors it is very easy to get lost troubleshooting this.

Re: What to expect from Debian/Trixie

#153
post #78

Earlier quoted context omitted.

14 different schemes multiplied by some acting slightly different in every version. Sure you can pin it, but that fixes only their internal back and forth, is only possible via the kernel cmdline and there is no guarantee for how long the old versions will stay available, as they deprecated much more invasive things in the past (e.g., cgroupv1) I'd expect them to also drop older versions here, breaking ones naming ag…

This worked brilliantly in Debian for more than a decade, had almost zero downside, and just did what asked. I went through 3+ dist-upgrades, for the first time in my life, without a NIC change. It was deprecated for this nonsense in systemd. Yes, there were edge cases in the Debian scheme. Yet it did work with VMs (as most VMs kept the same MAC in config files), and it was easy to maintain if you wanted 'fresh'. Jus…

systemd's design choices here were influenced by a lot of bugs Red Hat received where failed hardware was swapped out and interface names changed as a result. Real world enterprise users wanted this, it wasn't an arbitrary design choice.

Re: What to expect from Debian/Trixie

#154
post #95
post #81

Earlier quoted context omitted.

Not only that: Dovecot 2.4 will also remove the functionalities of dsync, replicator and director [1]. This is frustrating and a big loss as these enabled e.g. very simple and reliable two-node (active-active) redundant setups, which will not be possible anymore with 2.4. I use it for years to achieve HA for personal mail servers and will now have to look for alternatives -- until then will stick with Debian Bookworm…

You might be interested in https://codeberg.org/errror/dovecot-replication .

Thank you!

Re: What to expect from Debian/Trixie

#155
post #145

Earlier quoted context omitted.

This is exactly why I use Debian when I install Linux. I want something that will keep chugging along, yet may not have the most cutting edge software. I can take my time with the system, and know that it is solid. If I need newer software that isn't in their package repository, I understand that I have the ability to compile what I need, or at least make an active decision to modify my system to run what I want. Bas…

Exactly what I expect from the latest Debian. Boring and not working. Too many hacks by people who cannot work with upstream and have no idea what they are doing. But they are having their own good idea of a "proper" layout and package management.

Curious what you run, instead of Debian. I haven't had the same experience as you've had, but for myself, Debian has just worked other than having to provide my own wireless adapter driver .so file when I installed off a thumb drive without an Ethernet connection. While I have more experience than the average Linux user, and got started with Slackware in the 90's and then moved to Red Hat in the very late 90's, it's been a good 20 years since I used a Linux system full time. That's as a desktop, I've had no issues running as an application server for 2 decades.

I haven't run into a scenario where the desktop has caused me issues, only with Windows-only software that I sometimes require. What software has caused you issues that doesn't play nicely with Debian? What hacks are in place to mitigate upstream issues? I'm honestly curious, and if you don't use Debian, what distribution do you use regularly?

Re: What to expect from Debian/Trixie

#156
post #150
post #145

Earlier quoted context omitted.

Exactly what I expect from the latest Debian. Boring and not working. Too many hacks by people who cannot work with upstream and have no idea what they are doing. But they are having their own good idea of a "proper" layout and package management.

Exactly where is Debian "not working"?

Almost daily at work. Always have to verify with my fedora machines that it is indeed debian/ubuntu and not upstream.

Re: What to expect from Debian/Trixie

#157
post #143

Earlier quoted context omitted.

That seems like a bug with those applications which make use of the filesystem instead of performing in-memory operations or using named pipes.

"bug", more of a chosen design considering hardware constraints when things were designed.

So send a PR or have a distro level patch if that’s the issue.

Re: What to expect from Debian/Trixie

#158

Earlier quoted context omitted.

The page about upgrading [0] does have this warning: Back up your data Performing a release upgrade is never without risk. The upgrade may fail, leaving the system in a non-functioning state. USERS SHOULD BACKUP ALL DATA before attempting a release upgrade. DebianStability contains more information on these steps. [0] https://wiki.debian.org/DebianUpgrade

Yet Windows will let you roll back an upgrade with a single click within 10 days. Of course anyone can restore from backups. It's a pain and it's time consuming. My post serves more as a warning to those who may develop buyer's remorse.

If you keep your /home on a separate partition, you can basically reinstall a whole system without much efforts. It's good to do that from time to time. etckeeper is very helpful too. Lots of desktop apps are AppImage nowadays, so if you keep them in the home directory, they'll persist.

Re: What to expect from Debian/Trixie

#159
post #22
post #6

TIL there are 14 subtly different naming schemes for network interfaces[1]. "predictable" my ass. [1] https://manpages.debian.org/testing/systemd/systemd.net-nami...

The "stable" interface naming scheme is a scam. And I have proof. Test upgraded a VM today, from bookworm to trixie. And guess what. Everything worked, except after reboot the network interface was unconfigured? Guess what. The name changed...

[deleted]
Post reply on HN