Live data from Hacker News

Debian 11 “bullseye” freeze started

lists.debian.org

41–50 of 93 posts

Re: Debian 11 “bullseye” freeze started

#41
post #40
post #10

Earlier quoted context omitted.

I hope it means dropping the i386 distro, not dropping i386 multiarch which is still needed like for older 32-bit games and such. I don't see much value in i386 distro these days.

386 distro and i386 multiarch are pretty much one and the same for Debian, we don't have any "cut-down" ports without a kernel, bootloaders etc.

Well, then they shouldn't be. It's less of an overhead to maintain packages that focus on multiarch use cases and drop ones that focus on making it an i386 hardware targeted distro.

Re: Debian 11 “bullseye” freeze started

#43
post #39

I've been using Debian or Debian derived distros for quite a while, everything from straight up Debian on various servers, Armbian for my SBC's, to my secondary PC running Kubuntu and later KDE Neon. For me as a more casual Linux user, it's great as it essentially "just works" and I don't have to invest a great deal of time to fiddle with auxiliary things. However, if I could get one wish, it was to ditch the codenam…

If it helps, the list of Debian codenames is here: https://www.debian.org/releases/

Also the corresponding Devuan (systemd-free Debian) release names, with "Bullseye" equating to "Chimera":

https://www.devuan.org/os/releases

Re: Debian 11 “bullseye” freeze started

#45
post #44
post #5

Following the recent CentOS fiasco, I'm advising friends to go with Debian. It's rock solid and can be depended upon.

Fill me in? What recent fiasco?

CentOS as we know it is basically going away. Worse, they reneged on their promise of long-term support for the last release.

What will be known as "CentOS" will be the "stream" version, i.e. a rolling release distro with goals completely antithetical to what was out there before.

Re: Debian 11 “bullseye” freeze started

#46
post #44
post #5

Following the recent CentOS fiasco, I'm advising friends to go with Debian. It's rock solid and can be depended upon.

Fill me in? What recent fiasco?

CentOS 8 had its EOL brought forward to 2021 and CentOS 9 won't exist. Folks are expected to switch to CentOS Stream, RHEL or another distro.

https://lwn.net/Articles/839257/

Re: Debian 11 “bullseye” freeze started

#47

I've been using Debian or Debian derived distros for quite a while, everything from straight up Debian on various servers, Armbian for my SBC's, to my secondary PC running Kubuntu and later KDE Neon. For me as a more casual Linux user, it's great as it essentially "just works" and I don't have to invest a great deal of time to fiddle with auxiliary things. However, if I could get one wish, it was to ditch the codenam…

The code names make issues with specific versions or eras easy to search

Re: Debian 11 “bullseye” freeze started

#48

I've been using Debian or Debian derived distros for quite a while, everything from straight up Debian on various servers, Armbian for my SBC's, to my secondary PC running Kubuntu and later KDE Neon. For me as a more casual Linux user, it's great as it essentially "just works" and I don't have to invest a great deal of time to fiddle with auxiliary things. However, if I could get one wish, it was to ditch the codenam…

The code names make issues with specific versions or eras easy to search

Ubuntu at least does it in alphabetical order of the first letter of the codename. Eg, the release after Ubuntu 20.04 Focal was Ubuntu 20.10 Groovy. This means that hearing the Ubuntu codename "Bionic" provides some information: it was 4 releases before Focal.

But Debian codenames are arbitrarily based on characters from the movie Toy Story, so there's no relation to the Debian release.

To fix this, I propose for future releases the Debian codename naming scheme be replaced with numbers written out in words. Eg.

Debian 14 (fourteen)

Debian 13 (thirteen)

Debian 12 (twelve)

Debian 11 (bullseye)

Debian 10 (buster)

Debian 9 (stretch)

Debian 8 (jessie)

This retains the ability to easily search for eg, "Debian Thirteen", while making it much easier to remember earlier codenames as time goes on.

Also unlike Ubuntu's alphabetical naming scheme, the number approach doesn't have any overflow issues (which isn't as big of an issue anyway because Debian's provides new releases every 2 years instead of 6 monthly).

Re: Debian 11 “bullseye” freeze started

#49
I'm a big Debian fan. Every time someone asks me for "computer" help with their windows machines, I tell them I can only solve their problem installing Debian (which is true, I haven't used Windows in a long time).

So far my mom and dad have been using Debian for the last 4 years and I had to assist them almost never (we live in 2 different continents). Both of them work with the computer, and my dad is that person that is not good with computers.

I've also installed Debian to at least 6 friends, who never had a complaint again.

I also thought a friend how to code, she got a job as a developer after 9 months, she picked up Debian/linux super fast.

I hope it keeps getting better and better and easier.

Re: Debian 11 “bullseye” freeze started

#50

Anyone care to list the "things they wish were different" ? Trying to remember how to build a package some months back I ran into all the old headaches. Debian packaging is ancient, and the packages don't provide all the information and functionality other package management formats do. Trying to contribute a package (much less write one) is a pain. The structure of the files and how to build them seems over-complica…

The author of i3 Windows Manager has a series of interesting blog posts about his pain points with Debian project. [1] Well worth reading the blog series.

He also has a research distribution named 'distri' that tries to fix certain aspects of those pain points. [2]

[1] https://michael.stapelberg.ch/posts/2019-03-10-debian-windin...

[2] https://michael.stapelberg.ch/posts/2019-08-17-introducing-d...

Post reply on HN