Re:Bus1: a new Linux interprocess communication proposal
by IshKebab on Thursday August 18, 2016 @07:38AM
(#12311677)
Yeah but is it possible to run very old binaries on a current kernel? Unlikely. What about binaries compiled on a newer system than your own? Even less likely.
Re:Bus1: a new Linux interprocess communication proposal
by majewsky on Thursday August 18, 2016 @04:31AM
(#12311087)
Well yeah, most of the libc API is older than Linux.
Re:Bus1: a new Linux interprocess communication proposal
by ekidd on Thursday August 18, 2016 @07:00AM
(#12311549)
The Linux libc API changed a couple of times in the 1990s (a.out → ELF, libc5 → libc6, etc), but the Linux kernel ABI (what libc uses to talk to the kernel) has been stable since practically the beginning. Linus detests breaking anything that talks to the kernel and considers it massively unprofessional, to the point that even a terrible API will be set in stone if anything uses it.
Re:Bus1: a new Linux interprocess communication proposal
by Annatar on Wednesday August 24, 2016 @02:50PM
(#12354317)
What about drivers?
On SunOS, I can install a driver built on SunOS 5.5.1 (Solaris 2.5.1) on the latest illumos or Solaris-based OS, without recompilation, thanks to the device driver interface / device driver kit ("DDI / DDK"). Solaris 2.5.1 came out in 1993; illumos came out, well, today (multiple commits every day).
Is the same possible on GNU/Linux?
And while all that is constantly changing, its still possible to compile very old user space software and run it in on a current kernel.