Re:If there's no 16-bit layer in 64-bit Windows, how come 16...
by thwarted on Sunday November 03, 2013 @08:30PM
(#6666156)
You make your linux binary executables future-proof by statically linking them. It's a rare event that it happens, but I've no problems with 15 year old a.out binaries on 64-bit systems.
[ Parent
| on HN ]
Re:If there's no 16-bit layer in 64-bit Windows, how come 16...
by anyfoo on Monday November 04, 2013 @11:59AM
(#6669641)
As soon as they use for example, say, utmp, they will break. Worse, they might trash your utmp. The utmp format was changed with the transition from libc5 to glibc 2, to support IPv6. You might not care too much about utmp nowaways, but it's an example for something which changed.
Also, your 15 year old statically compiled binary will contain every little bug any of the linked in libraries had those 15 years ago.
Re:If there's no 16-bit layer in 64-bit Windows, how come 16...
by thwarted on Monday November 04, 2013 @07:50PM
(#6672329)
And this is the trade off you make for not having the source, but it doesn't negate it as a method to keep things running for longer. If you should keep things running, without having the source, for that long, is another issue.