Live data from Hacker News

Debian 13 “Trixie”

debian.org

111–120 of 428 posts

Re: Debian 13 “Trixie”

#111
post #93

Earlier quoted context omitted.

>I've never had a Debian system break without it being my fault in some way. Debian is great but I can't say this is a shared experience. In particular, I've been bitten by Debian's heavy patching of kernel in Debian stable (specifically, backport regressions in the fast-moving DRM subsystem leading to hard-to-debug crashes), despite Debian releases technically having the "same" kernel for a duration of a release. In…

Which GPU, display server and compositor stack are you using?

Integrated Intel GPU and no graphical system, just KMS VT (text console). That's what made it so frustrating - only displaying a console should not result in kernel panics under CPU load! Admittedly, the experience was anecdotal and years ago and I heard Debian is doing less of a RHEL-style "frankenkernel" now.

Re: Debian 13 “Trixie”

#112
post #17

> i386 is no longer supported as a regular architecture: there is no official kernel and no Debian installer for i386 systems. The i386 architecture is now only intended to be used on a 64-bit (amd64) CPU. Users running i386 systems should not upgrade to trixie. Instead, Debian recommends either reinstalling them as amd64, where possible, or retiring the hardware. Impressive that i386 support made it all the way to A…

Hopefully i386 (or perhaps a new i386-like port with added support for 64-bit time values) can move to the unofficial Debian Ports infrastructure for Debian 14 (forky) or Debian 15 (duke). Debian Ports has a m68k port, so supporting one for i386 shouldn't be a huge problem.

The i386 architecture hasn't been dropped, it is still available in the archives to support 32-bit applications. The major change is that there no longer is a 32-bit kernel in the archive (the package linux-image-686 is no more). But most packages are still available in their i386 versions:

  $ curl -s http://deb.debian.org/debian/dists/trixie/main/binary-amd64/Packages.gz | zgrep ^Package: | wc -l
  68737
  $ curl -s http://deb.debian.org/debian/dists/trixie/main/binary-i386/Packages.gz | zgrep ^Package: | wc -l
  66958

Re: Debian 13 “Trixie”

#113

Writing this from my Debian system, it's a great distro that has been excellent to me as a daily driver. I switched to Debian 6 after Ubuntu went way downhill and haven't had cause to regret it. I like Debian's measured pragmatism with ideology, how it's a distro of free software by default but it also makes it easy to install non-free software or firmware blobs. I like Debian's package guidelines, I like dpkg, I lik…

Yeah, I ditched Ubuntu Server after too many upgrade headaches. I manage 75+ VPS instances for app hosting, and it's nerve-wracking doing maintenance updates knowing there's a chance one won't boot after. That's easily an extra 1-2 hours per VPS just to get it back. Switched to Debian back in the 8.x days in 2015 and it's been smooth sailing. Never had it break unless I was the one who messed it up.

Re: Debian 13 “Trixie”

#114

Earlier quoted context omitted.

Snaps? Proprietary package managers are never great.

As I understand it, snap the package format is not proprietary. Its as open source as say flatpak. What is proprietary is Canonical official snap store, and they patch their version of snap to only use that store. It'd be the same as flatpak being tied to only flathub. Of course that goes against the spirit of FOSS, but there's a bit more nuance there than simply saying "snaps are proprietary".

Snaps don't just suck from an ideological but also practical perspective, as described for Thunderbird. Firefox on Ubuntu has also serious permission issues with webcam support OOTB even experts are struggling with (involving AppArmor, pipewire, snap, and FF device config). and has become unusable for things like browser-only MS Teams on mainstream notebooks.

Containers, popular as they may be on servers, can only add breakage and overhead to desktops, especially for an established and already much better organized system like Debian's apt. There just haven't been any new desktop apps for way over a decade that would warrant yet another level of indirection.

Re: Debian 13 “Trixie”

#115
post #111

Earlier quoted context omitted.

Which GPU, display server and compositor stack are you using?

Integrated Intel GPU and no graphical system, just KMS VT (text console). That's what made it so frustrating - only displaying a console should not result in kernel panics under CPU load! Admittedly, the experience was anecdotal and years ago and I heard Debian is doing less of a RHEL-style "frankenkernel" now.

Intel's integrated GPU driver team, actually all driver teams, had a period of frequent screw-ups a while back (five years ago? Time flies). They also borked e1000e driver in the same period.

On the other hand, I had and still have many Debian installations, some with Intel integrated graphics. None of them created any problems for a very, very long time. To be honest, I don't remember even any of my Intel iGPU systems crashed.

...and I use Debian for almost two decades, and I have seen tons of GPU problems. I used to write my Xorg.conf files without using man, heh. :)

Maybe you can give Debian another chance.

Re: Debian 13 “Trixie”

#116
I love Debian and have a tremendous amount of respect for the people who work on the project. I no longer use Debian, but I think it's vitally important to have an anchor Linux distribution which isn't overly reliant on a for-profit entity and is truly community driven.

Re: Debian 13 “Trixie”

#117
post #96
post #17

> i386 is no longer supported as a regular architecture: there is no official kernel and no Debian installer for i386 systems. The i386 architecture is now only intended to be used on a 64-bit (amd64) CPU. Users running i386 systems should not upgrade to trixie. Instead, Debian recommends either reinstalling them as amd64, where possible, or retiring the hardware. Impressive that i386 support made it all the way to A…

Are you confusing "386" with 32bit? 686 is the normal 32bit arch. 386 is something from the 1980's right?

When distros mention i386 support they often actually refer to i586 or i686, yes.

True i386 support would mean compatible with the original Intel 386 processor from 1985. The 486 added a few additional instructions in 1989 but things really changed with the Pentium in 1993 - that gave us i586 which is the bare minimum for most modern software today. Much software can still run on regular Pentiums today if compiled for it, but SSE2 optimizations requires at least a Pentium 4 or Core CPUs instead.

I play with retro PCs often and found OpenBSD's i386 target stopped supporting real 386 CPUs after the 4.1 release, and dropped support for i486 somewhat recently in 6.8. It now requires at least a Pentium class CPU, i586, though the arch is still referred to as i386 likely because it's a common proxy for "32-bit".

Re: Debian 13 “Trixie”

#118
post #9

I can't believe we've come to such a high number, and a particularly lucky one at that Alas it's still not suitable as a daily driver for the average home user and probably never will be. It is unfortunate that Ubuntu has to reign supreme in that regard.

You can install debian and ubuntu with same DE and you'd be hard pressed to find a difference apart from the theme unless you are a power user who knows what snap is. In fact, Ubuntu has never been an especially user friendly distro. At the beginning it was just a debian that was installed with debian's experimental installer before they decided to use it in stable. Nothing more, nothing less. If you wanted to find a…

>The only specific thing Ubuntu did for beginners is sending CDs for free

Assuming you are not malicious I will kindly help with your bad memory, Ubuntu had always very good proprietary driver support, this made laptops actually work and helped beginners. I also remember they had a graphical installer compared to Debian and for sure this was beginners friendly. Maybe some other distro offered easy way to install and come with proprietary drivers setup but I can't remember a deb based distro doing that.

Anyway you were wrong, the CDs were not the only thing made Ubuntu appeal for beginners, there were Linux magazines with CDs each month and they were not super expensive , my first linux was a Kubuntu 6.10 from a magazine and I am still running Kubuntu today though i ran Debian, Sidux, Arch, Mandriva, SUSE in the past when I had time to try different distros, compile custom kernels etc.

Re: Debian 13 “Trixie”

#119

Plasma 6.3 - I can finally ditch kde neon.

Not if you want to remain on new Plasma, you can expect Debian to lag several minor versions behind.

I've found it pretty easy though to use some KDE components built from source on top of the standard Debian packages. Build with kdesrc-build, then have those binaries linked to from your ~/bin and you're set. It might get difficult if you want to rebuild some key components like plasmashell itself but I've been using locally built versions of Kate and Konsole without issue.

Post reply on HN