Re: Get rid of them

H. Peter Anvin (hpa@transmeta.com)
25 Aug 1997 17:08:48 GMT


Followup to: <Pine.LNX.3.96.970825113433.17532B-100000@sub994.sub.uni-goettingen.de>
By author: Marcin Dalecki <dalecki@sub994.sub.uni-goettingen.de>
In newsgroup: linux.dev.kernel
>
> And just a hint why the current development kernel 2.1 isn't that backward
> compatible below libc-5.4.13 anyway:
>
> 1. Error return value handling!!! (Do You remenber the grief????)
>
> 2. Memmory mapping changes 0xC0000...00 (Don't remember haow many zeros :-).
>
> 3. modutils-2.1.42 and anything else module related.
>
> 4. Anything /proc related Tough I'm not a friend of the not very well done
> design of this interface. It's fluctuating just too frequently.
>

1-3 mainly apply to modules, which only affect a handful of binaries;
those binaries can be considered "system binaries". /proc, well,
could be a problem, but most user applications only look at
/proc/loadavg which have grown smoothly. /proc/meminfo is probably
the biggest problem, but the old /proc/meminfo was just too broken...

That doesn't mean we should start throwing out random things because
"I'm not using them anymore." THE biggest complaint commercial
vendors have had with Linux has been the instability of the ABI, and
this is something we need to be very, very sensitive to. I heard
someone say, not too long ago, that two years was a reasonable time to
keep the ABI compatible. That is nonsense -- 5 years is a minimum,
and I would go for 10 years. Especially for corporations with
in-house software, running a two-year-old binary next to a brand new
one is an everyday occurrence.

-hpa

-- 
    PGP: 2047/2A960705 BA 03 D3 2C 14 A8 A8 BD  1E DF FE 69 EE 35 BD 74
    See http://www.zytor.com/~hpa/ for web page and full PGP public key
Always looking for a few good BOsFH.  **  Linux - the OS of global cooperation
        I am Baha'i -- ask me about it or see http://www.bahai.org/