@Carolina In My Mind

Way ahead  of you. I currently run a thinkpad t430s, have been almost a year. Its the fact that a laptop built in 2022 and cost almost a grand couldn't be worth a damn that I was really aggravated about. For me the main thing is the touchpad. So big, bulky, and buttonless...its a pain in the ass to use.

For those who don't like reading past headlines...

It very explicitly says that there are no plans for it to be the default. Many architectures and platforms Debian is installed on couldn't even *use* systemd-boot, because they do not have UEFI. They're improving support for something, whoopty-do...besides, wasn't there a discussion a while back about making a standalone package in Devuan for it? I seem to recall doing a bit of research on that at one point...

'Sides, by the time things progress to the point that its all UEFI-only, I'm pretty sure most legacy-only machines will either be dead, dying, or too weak to handle a modern linux installation and still be reasonably useful. Hell, even the Kernel is reaching a critical mass at this point...

Of all the things to worry about right now (*cough* Windows Recall *cough*), this is the least of them

@mrnhmath may I suggest...codeberg?

@GlennW This is because you need to do one of two things, which I completely forgot to add to the above:

In order to NOT have issues with the untrusted CDROM source (Neither Debian nor Devuan can furnish release files in them, it would be pointless since they are static), you have to do one of the following...

When you update with apt, do

sudo apt update --allow-insecure-repositories

OR, alternatively, in /etc/apt/sources.list, change the cdrom entry from

deb cdrom_source_name daedalus main 

to

deb [trusted=yes] cdrom_source_name daedalus main

I hope this helps! It will not cover all of your packages if you installed something outside of the CDROM from chimaera, but even if you only use this in conjunction with internet access on the actual daedalus repos, it can STILL save you trouble by not having to waste bandwidth on the packages you already have stored on the CDROM.

I should also mention that the above about saving bandwidth is also applicable to the server and netinstall ISO's, you can use those too!

This is the first I've seen of any real experimentation with s6 beyond GNUinos, this should be pretty interesting...maybe someday it'll be solid enough to upstream to Devuan? That'd be cool.

NVIDIA has historically not played nice with suspend. I have an old T61p that has NVIDIA graphics, and it doesn't suspend correctly, either.

I second this version

My first distro was Ubuntu 18.04. I have fond memories of her, genuinely, and i owe what I know today to that first experience. But alas, it also made me understand why systemd was so terrible, and regarding Ubuntu she has gone down the shitter the last two major releases. Its a sad, sad state.

This has been discussed before:
https://dev1galaxy.org/viewtopic.php?id=4131

^I'd just like to pitch in to the above and add, so does Void Linux

I suppose this was bound to happen eventually, but admittedly I was not expecting this to happen this quickly. The last 686 CPUs were released in 2006, and the latter-day ones I have are still reasonably capable for their age...

Interestingly, having read the actual Debian announcement, they do not plan to make it a partial architecture like Ubuntu does -that's up to the package maintainers themselves. And from the sound of it, i386 could also possibly get relegated to the Ports branch. With this in mind, I feel like *maybe* some more-determined distros could continue i386 support at least for Trixie, depending on how bad things get between now and release. Best (read: highly unlikely) case scenario, all they need to supply is a kernel. Not a difficult task, by any means. More Likely case scenario: quite a few packages will bite the dust between now and then, and would need to be re-compiled, if they still can be. I get a feeling the browsers will be the first to go. the feasibility of such an endeavor goes back to the question of: What's the damage gonna be, come release time?

As long as the Init Diversity Team isn't abolished, and Snaps don't become the new default in Debian, we should be ok for now. Though it might be time for Devuan to give a bit more love to its other ports, in i386s' place...

Don't forget http://deb.devuan.org/bannedpackages.txt , so people have a sense of what packages might be worth making compatibility packages/patches for