On 2/16/21 11:08 PM, L A Walsh wrote:
Is suse supporting this model for enterprise
customers? I can't
believe they would tolerate it.
No, SLE has different upgrade mechanisms which provide defined upgrade
paths. A rolling release distribution naturally doesn't follow that
model and breaking changes are the very nature of a rolling release
I can take programs in Win from 10-20 years ago and
they still work
on a current day win because the OS loads library updates by version.
That's actually not true. Microsoft fixed a lot of bugs in their ABI over the
time and dropped support for various older ABIs when they switched to 64 bit
Windows or rewrote fundamental subsystems such as the graphics or sound stack,
so that a lot of older programs don't work anymore.
I think there even used to be a WINE on Windows port to address this issue
and allow older Windows applications on newer versions of Windows.
Unix did the same -- but move to linux, and vendors
got lazy and stopped
using the correct versions to link with. Why? And how can this be fixed?
Actually, you can run 30-year-old binaries on a current version of Linux as
long as you provide the necessary shared libraries or the application is
statically linked since the Linux kernel guarantees to never break any userspace