On Sun, 9 Jan 2000 kuznet@ms2.inr.ac.ru wrote:
> Hello!
>
> > > > what breaks and fix it. (Beginning around 2025.)
> >
> > > This should be step 1.
>
> 8)
>
> Guys, what do you smoke? Gimme too, please. 8)
> Please, learn to plan something for 1 day, then week, then month
> for beginning. After this you will understand that planning for
> 40 years is impossible in cube.
>
This is my point.
To plan that (probably someone else) will perform a critical
fix in 25 years is ludicrous. The fix needs to be performed ASAP,
so that userspace developers with broken code will have to
fix it NOW, not in 25-30 years.
Current systems have the processor power to spare, and if broken code is
allowed to accumulate it will.
Note that changing time_t will have NO IMPACT on currently installed
systems, it will have an effect only on upgrades. So if someone is
dependent on broken code and can't get it fixed, they just run a dist
from before the update. The old code doesn't magicly disappear just
because Linus issues a patch...
Daniel Taylor
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Jan 15 2000 - 21:00:16 EST