Live data from Hacker News

Debian 13 “Trixie”

debian.org

311–320 of 428 posts

Re: Debian 13 “Trixie”

#311
post #67
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.

You uninstall all snaps, uninstall snapd, and block it from being installed via APT.

Then you add e.g. the mozilla PPA such that its firefox package gets installed instead.

Re: Debian 13 “Trixie”

#312

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…

Debian is my foundation. I keep servers on Old Stable and test new release features on an ephemeral system. I learned nftables with Bookworm and labwc with Trixie. labwc supports Wayland with Openbox configuration.

Why do you remain on old stable instead of stable?

Re: Debian 13 “Trixie”

#313
post #270
post #251

Earlier quoted context omitted.

It baffles me I keep searching for these files every time I want to download Debian. And it’s been like that for over a decade at least.

They are linked from the "Other downloads" page linked from the front page.

Yeah, I think I remember that, but each time I’m puzzled and not sure. It feels like they hid that deliberately. While Arch is the opposite, it’s so easy to get the torrent file.

Re: Debian 13 “Trixie”

#314
post #14

You can still use sysvinit, I've already tested servers and desktop builds. From my build box: chroot $MOUNTPOINT/ /bin/bash -c "http_proxy=$aptproxy apt-get -y --purge --allow remove-essential install sysvinit-core sysvinit-utils systemd-sysv- systemd-" There is a weird depends you cannot get around without simultaneously removing and installing in parallel. A Debian bug highlighted the above, with a "-" for systemd…

Wait, sysvinit on debian 13 truly practically works?? as in, one can remove systemd and have a working server OS with sysv init??

Yes, MX Linux will be doing this (as a separate ISO, until now they're been able to provide a single ISO that lets you choose between systemd and sysvinit at every boot):

https://mxlinux.org/blog/changes-coming-with-mx-25/

Re: Debian 13 “Trixie”

#315

Debian's signature feature (upgrade from stable to stable under 15 minutes) shines here too. My first system migrated in less than 10 minutes, incl. package downloads and reboot. It's not a beast either. N100 mini PC connected to a ~50mbps network.

What was the process for this? Does it involve manually modifying the sources.lists files, or is there a single command to instigate the upgrade?

There are two main ways:

If your sources file references the release name (e.g.:bookworm), you change them to trixie, then “apt update && apt dist-upgrade”.

or,

If your sources file directly reference distro-suites (e.g.: stable), you just “apt update && apt dist-upgrade” since stable is now pointing to trixie.

In the first reboot, you run “apt autopurge” to remove packages which are not needed anymore.

…and you’re done.

Re: Debian 13 “Trixie”

#316
post #79

As an owner of two i386 systems (both netbooks built around Intel's Atom N270), that run Debian, I am a little sad. I understand the reasoning, and I won't deny it is a very niche platform by now. But I had hoped Debian, with a history of supporting a wide range of platforms, would keep i386 going for a while longer. Fortunately, bookworm will continue to receive updates for almost 3 years, so I am not in a hurry to…

antiX will be creating a Trixie-based 32-bit ISO. There's also Void, Alpine and Slackware (at least).

Re: Debian 13 “Trixie”

#317
post #275

Earlier quoted context omitted.

Out of curiosity, what do you use these netbooks for?

One sits in my bathroom so I can browse random Wikipedia articles while I'm, uh, busy. The other one sits on my nightstand and plays audiobooks/podcasts when I'm going to sleep. So nothing critical. But something they are still good at, and being very small makes them a natural fit for these use cases.

Curious, why not use your phone for both these use cases? Seems like it would be even more convenient

Re: Debian 13 “Trixie”

#319
post #176
post #172

Earlier quoted context omitted.

Canonical did their own NIH init daemon called Upstart which failed due to the fundamental design and the implementation being plain bad. Redhat builds better software which is why their NIH gets more adoption.

ChromeOS still uses upstart.

Upstart came before systemd; much of the reason for systemd’s creation was fixing what was considered fundamental design mistakes in Upstart: http://0pointer.net/blog/projects/systemd#:~:text=On%20Upsta...> (under the heading “On Upstart”).
Post reply on HN