Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Debian 13 “Trixie”

debian.org

Post reply on HN
Print view View original

211–220 of 428 posts

Re: Debian 13 “Trixie”

#211

Post by yjftsjthsd-h »

kasabali wrote: post #128
madars wrote: 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…

> Debian's heavy patching of kernel in Debian stable Needs citation. Debian stable uses upstream LTS kernels and I'm not aware of any heavy patching they do on top of that. Upstream -stable trees are very relaxed in patches they accept and unfortunately they don't get serious testing before being released either (you can see there's a new release in every -stable tree like every week), so that's probably what you've…

AFAICT, the patches are here: https://salsa.debian.org/kernel-team/linux/-/tree/debian/lat...

Whether that qualifies as "heavy" or not is of course a matter of opinion, but it's not nothing.

Re: Debian 13 “Trixie”

#212

Post by JackeJR »

rbanffy wrote: post #152
ACS_Solver wrote: post #25

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…

The only thing I can say against Debian is that it tends to start new server software immediately after install, before I have a chance to configure it properly. Defaults are sane for most packages, but, still, it scares me a little. In that I like the Red Hat approach of installing and leaving it off until I decide to turn it on.

Just have sane firewall rules and you are good. E.g. if I install openssh-server and it auto starts, it doesn't make it out of my machine because my nftables does not allow inbound on port 22. It's just knowing the default behaviour and adjusting your practices for it.

Re: Debian 13 “Trixie”

#213

Post by int_19h »

I see that systemd is still doing this thing where they are trying to strong-arm all Linux distros into arbitrary stuff that someone decided is the only right way to do something:

> 5.2.2. systemd message: System is tainted: unmerged-bin systemd upstream, since version 256, considers systems having separate /usr/bin and /usr/sbin directories noteworthy. At startup systemd emits a message to record this fact: System is tainted: unmerged-bin. It is recommended to ignore this message. Merging these directories manually is unsupported and will break future upgrades. Further details can be found in bug #1085370.

No option to disable this either, per discussion in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085370

Re: Debian 13 “Trixie”

#214

Post by justinclift »

tasuki wrote: post #67
mmcnl wrote: post #49

Earlier quoted context omitted.

I don't really understand why this is such a big problem. You don't have to use snaps.

I'm with my neighbor comments. How do you use Ubuntu without snaps? The base Ubuntu install already comes with several snaps. Installing random things through apt leads to snaps. I personally do not know how to avoid snaps on Ubuntu.

I made this snap "alternative" to solve this exact problem: https://github.com/justinclift

Packaged as: https://github.com/justinclift/snapd-empty/releases/download...

It's just an empty package that tells the system snap is installed, to stop the broken dependency chains you otherwise get from force uninstalling snap.

It's been working fine on a handful of Ubuntu 24.04 systems I've been handed and can't change the OS of, for about half a year now.

Re: Debian 13 “Trixie”

#216

Post by vwwvwvwv »

ACS_Solver wrote: post #25

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…

[flagged]

Re: Debian 13 “Trixie”

#217

Post by specproc »

porridgeraisin wrote: post #206
WD-42 wrote: post #183

Earlier quoted context omitted.

One of the unsung praises of Arch is that it's turned thousands of users into testers. Before someone says "that shouldn't be the user's responsibility" I'm going to say I'm not so sure. We're all in this together. I'd rather deal with a bug or two on my desktop at home if it means it gets fixed before appearing in a distro that gets used for servers at work and causes issues there where the consequences are much hig…

I have a similar experience. My not-so-tech-savvy brother also has the same laptop setup I do (arch+XFCE). He knows to yay -Syyu and it's usually never a problem. The recent upgrade there was the vlc package split problem so I told him to hold on upgrading and that I'd come and do it. While I needed to sit and filter and install the optional dependencies myself for my upgrade, a week later it was already figured out…

I don't consider myself particularly adept with linux. I've only been running it daily on the desktop for the last few years and, aside from mucking around with TWMs, I've not done much poking about with the internals.

Despite the reputations, I've had far fewer issues on Arch-based desktop distros than back when I was rolling Ubuntu and Debian.

That said, Debian on a server every time.

Re: Debian 13 “Trixie”

#218

Post by porridgeraisin »

specproc wrote: post #217
porridgeraisin wrote: post #206

Earlier quoted context omitted.

I have a similar experience. My not-so-tech-savvy brother also has the same laptop setup I do (arch+XFCE). He knows to yay -Syyu and it's usually never a problem. The recent upgrade there was the vlc package split problem so I told him to hold on upgrading and that I'd come and do it. While I needed to sit and filter and install the optional dependencies myself for my upgrade, a week later it was already figured out…

I don't consider myself particularly adept with linux. I've only been running it daily on the desktop for the last few years and, aside from mucking around with TWMs, I've not done much poking about with the internals. Despite the reputations, I've had far fewer issues on Arch-based desktop distros than back when I was rolling Ubuntu and Debian. That said, Debian on a server every time.

Yeah same. I think the release cycle actually doesn't matter at all. The reason for it is that the majority of breakage are caused by components/extensions of gnome and kde and non-DE-yet-complex software in distros with a lot of those present out of the box, like manjaro, breaking backwards compatibility every other week.

When people switch to arch they typically set things up from scratch, end up choosing simple tools and avoid most of the unstable stuff distros push onto you.

Re: Debian 13 “Trixie”

#219

Post by ilvez »

Nice, more chaos to unstable again. Sincerely happy because of the release and new stable, but also selfishly happy because now unstable starts moving again.

Re: Debian 13 “Trixie”

#220

Post by avhon1 »

winrid wrote: post #189
accrual wrote: 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…

Man, I thought I was behind using a P3 in like 2007 lol. You can get something 100x faster for $1 :D

Debian (and many other distributors of compiled binaries) uses "i386" to refer to all 32-bit x86 processors, including the Pentium 3.
Post reply on HN