News for hackers. Stuff that matters.
Re:Debian 11 “bullseye” freeze started by Mathnerd314 on Thursday January 14, 2021 @09:32PM (#25786244)
They're considering dropping i386, which is interesting. Does anyone know more about that?
Re:Debian 11 “bullseye” freeze started by cipherboy on Thursday January 14, 2021 @09:41PM (#25786306)
Re:Debian 11 “bullseye” freeze started by mappu on Thursday January 14, 2021 @10:37PM (#25786705)
Time64 is the death of i386 - the time_t structure needs to be expanded to 64-bit to handle dates beyond 2038, but that's an ABI break, and the primary reason anyone still runs 32-bit binaries is for closed-source games which won't come along for an ABI upgrade.

You can either do the ABI break and lose most existing users when the main set of apps stop working, or have the main set of apps stop working anyway in 2038.

Re:Debian 11 “bullseye” freeze started by ncmncm on Thursday January 14, 2021 @10:55PM (#25786828)
You could switch it to unsigned 32-bit time_t, and most things would still work right up to 2106.

With any luck, civilization will collapse by 2038 and it won't matter anyway. But, struggling back up from collapse on scavenged 32-bit microcontrollers powered by scavenged solar panels, we won't need the extra burden of post-y2038. Switch to unsigned 32-bit time_t for the sake of the (surviving) grandkids.

Re:Debian 11 “bullseye” freeze started by jabl on Friday January 15, 2021 @02:38AM (#25788081)
You keep saying this, but you're too late. The 64-bit signed time_t path was already chosen long ago and is being implemented.
Re:Debian 11 “bullseye” freeze started by ncmncm on Friday January 15, 2021 @11:14AM (#25792470)
Not on those.
Re:Debian 11 “bullseye” freeze started by jabl on Friday January 15, 2021 @02:37AM (#25788073)
The kernel has already been fixed, but userspace (glibc) is AFAICS still in progress. Glibc is going to do it in a similar fashion to large file support (LFS), where if you define some particular macros you get the 64-bit time_t interfaces, otherwise you'll continue with the old 32-bit time_t. Similarly, existing binaries will continue to work, so in order to take advantage of 64-bit time_t you need to recompile (with those macros set, and fixing any resulting problems of course).
Re:Debian 11 “bullseye” freeze started by shmerl on Thursday January 14, 2021 @09:53PM (#25786410)
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.

Re:Debian 11 “bullseye” freeze started by pabs3 on Thursday January 14, 2021 @11:32PM (#25787031)
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.
Re:Debian 11 “bullseye” freeze started by shmerl on Thursday January 14, 2021 @11:35PM (#25787055)
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 by megous on Thursday January 14, 2021 @11:22PM (#25786970)
Debian keeps IBM Thinkpad T41 alive. :)
Re:Debian 11 “bullseye” freeze started by lmm on Thursday January 14, 2021 @09:56PM (#25786431)
I'm guessing that fewer maintainers are running i386 to the point where i386 is not "tested by default". So they're asking porters to step up and take over testing/maintaining packages for i386 if they want the i386 releases to continue.
Re:Debian 11 “bullseye” freeze started by pmarin on Friday January 15, 2021 @02:11AM (#25787924)
Can you provide a link about this?
Re:Debian 11 “bullseye” freeze started by HDMI_Cable on Thursday January 14, 2021 @09:36PM (#25786273)
I think it may be because the software packages for i386 are closed-source, but don't quote me on that.
Re:Debian 11 “bullseye” freeze started by freeone3000 on Thursday January 14, 2021 @09:54PM (#25786412)
It's because in 2021, i386 processors are obsolescent. The last non-amd64 processor that ran x86 is the Pentium 4E from 2004, a 17-year-old machine. The packages will still be available as long as there's a maintainer, but it's not worth packaging a full debian release for such a small and shrinking portion of the userbase.
Re:Debian 11 “bullseye” freeze started by lmm on Thursday January 14, 2021 @10:03PM (#25786486)
> The last non-amd64 processor that ran x86 is the Pentium 4E from 2004, a 17-year-old machine.

Atom CPUs without x86_64 support were released up until 2013.

Re:Debian 11 “bullseye” freeze started by realdense on Friday January 15, 2021 @12:56AM (#25787511)
Debian Buster LTS is supported until 2024 and then probably ELTS until 2026. Also how many of these 32-bit Atom CPUs are actually in use anymore? It's a pretty edge case.
Re:Debian 11 “bullseye” freeze started by arpa on Friday January 15, 2021 @01:50AM (#25787790)
I run my home automation on atom. Considering that cost of asus eee pc is around $70 it still is a lucrative option of a complete system compared to raspberry.
Re:Debian 11 “bullseye” freeze started by lmm on Friday January 15, 2021 @01:28AM (#25787680)
Debian is (or at least used to be) popular for old hardware - e.g. they supported m68k for longer than most distros. I had an i386 Atom netbook that I was using up until about a year ago, and if I hadn't moved internationally I'd probably still use it.
Re:Debian 11 “bullseye” freeze started by walrus01 on Thursday January 14, 2021 @10:03PM (#25786492)
The Intel Core Duo (such as found in the 1st generation Intel macbook pro) from 2006) is not 64-bit capable.
Re:Debian 11 “bullseye” freeze started by flukus on Thursday January 14, 2021 @11:05PM (#25786879)
But i386 will still run on 64 bit hardware. A place I was working recently was insisting on sticking to 32 bit linux while they migrated off Solaris, mostly for stupid reasons on code that wasn't too hard to port, but just because the hardware is no longer compatible doesn't mean the software is, especially for any proprietary software that will never be upgraded.