@mcc in terms of supporting security long term: it was done by a project called Linux-CIP. But the Linux-CIP style project is only possible if there's sensible CVE reporting in upstream and the possibility to port the patches. The new policies, as I said, mean that everything is potentially and maybe even likely to be tainted
@nina_kali_nina
Are you sure ABI/API are unstable? I have compiled a niche script interpreter on Linux 2.?.? and same binary did run on my recent Linux installation, which was 5.? or 6.? then. I remember that I had to backport the program to the old libc, but it was doable.
I suppose the „glue“ is libc which has to fit the kernel.
@mcc
@hierkiosk @mcc I wouldn't be surprised if libc was doing a lot of heavy lifting there. I also wouldn't be surprised that for relatively simple applications there wouldn't be any problems with running a program that was statically compiled for 2.6.x on 5.x or 6.x kernels. However, I doubt it'll be easy to run a program compiled and linked for 5.x kernel on an older kernel. Stuff like that is a problem for both emulation layers (NetBSD compat_linux and FreeBSD Linuxulator) and hard forks (that will either have to stay somewhat frozen in time or will have to catch up to the upstream). E.g. let's say Valve ships a new Steam version that requires kernel 7.2 - this will happen almost inevitably; how much work will be needed to figure out what parts of the Linux 7.2 need to be re-implemented in the fork and in the emulators?
@nina_kali_nina @hierkiosk @mcc I would rather wager that the program had run without changes if it hadn't depended on glibc in the first place.
Compared to whatever the hell glibc does, kernel ABI is rock-solid.
@nina_kali_nina @mcc Also, Linux-CIP works on a heavily restricted set of industrial-grade hardware; if you're not a sponsor, your machine very likely isn't supported.
For instance, Linux 4.4 on CIP only works on two architectures (can't remember which) and only on specific hardware.
It's meant for big actors (like the railway or medical industries) who absolutely cannot upgrade the kernel beyond mandatory security patches because of certifications/safety constraints.