Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 23, 2013
An "enum" for Python 3
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
Seems like that could be a good idea at some point.
In that case, 2.6 would need at least basic maintenance for at least 10 years.
Posted Sep 6, 2008 14:45 UTC (Sat) by addw (guest, #1771)
How about changing the ELF magic number in some way to bring in a compatability layer ? OK: this does somewhat defeat the object, but all the depricated API could be kept in one module (hopefully rarely loaded).
This would allow old binaries to run.
I suspect that most programs would be OK on a recompile, only a few would genuinely break since they rely on really old/removed bits of the kernel API.
What do we do about bits of /proc that change ?
It would be nice if some kind of warning message could be generated in advance so that we would know what would break.
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds