Debian discusses how to handle 2038
Debian discusses how to handle 2038
Posted Feb 20, 2020 22:00 UTC (Thu) by flussence (guest, #85566)Parent article: Debian discusses how to handle 2038
Posted Feb 21, 2020 3:44 UTC (Fri)
by nivedita76 (subscriber, #121790)
[Link] (4 responses)
Posted Feb 21, 2020 5:16 UTC (Fri)
by ncm (guest, #165)
[Link] (3 responses)
Posted Feb 21, 2020 6:00 UTC (Fri)
by felix.s (guest, #104710)
[Link]
Until somewhat recently, I used Debian on a machine without SSE2 support. I was quite dismayed that I couldn't run the Rust toolchain on it, even though the compiler target is called ‘i686’.
That the current Debian architecture targetting 32-bit x86 is called ‘i386’ (which currently is i686 in fact) at least has the excuse of maintaining continuity/compatibility. If you go as far with making a clean break to rename the whole architecture, at least don’t pick a misnomer.
Though it’s not like such haphazard removing support for older machines doesn’t make me nervous. I still run Debian on an old 32-bit laptop, though that one at least does support SSE2. I do keep wondering when I’ll be forced to drop it.
Posted Feb 21, 2020 18:23 UTC (Fri)
by nivedita76 (subscriber, #121790)
[Link] (1 responses)
Posted Feb 23, 2020 6:35 UTC (Sun)
by flussence (guest, #85566)
[Link]
Yes that's not what i686 means. But in practice, most other distros seem to take it to imply AMD64 sans Long Mode. If Debian wants to continue to support the subset of x86 CPUs that glibc still supports && have PSE-36 && lack SSE, then I won't stop them. (Things like Rust might, unfortunately, but that isn't an i386-only problem.)
Debian discusses how to handle 2038
Debian discusses how to handle 2038
Debian discusses how to handle 2038
Debian discusses how to handle 2038
Debian discusses how to handle 2038