Agreed. Which is why, for the most part I noted that prime-time level
maintenance will not be the norm. Though *someone* I'm sure *will*
maintain it, even if they're the last person using it on the planet.
While 2.2 and 2.4 are usually after thoughts in that arena. *not all,
but most it seems*
> > The advancements which 2.6 will bring, over 2.4, will be extraordinarily
> > different, in terms of overall architecture it seems. Even if it's only
> > a 20% architecture difference from 2.4, think of how much further from
> > 2.0 that is.
>
> Yes, and that is why 2.0 is still maintained; for some users, the step
> between 2.0 and a later release is too large when it comes to how many
> userland programs that need to be upgraded/retested/rewritten.
That's true, but in my mind, except for embedded, these same users could
stand to probably upgrade their hardware as well, not just for speed
improvements, but capacity, and capability. This would most likely force
them into a new kernel to *properly* support newer hardware, or take
advantage of advancements that 2.0 can't offer.
> Really, there is little reason to worry; my contribution to the
> development of 2.5 (and a forthcoming 2.6/2.7/2.8/...) would probably
> not be much larger were I to drop maintenance of the 2.0-tree. Possibly,
> Marcello and Linus would receive a few more odd fixes for typos and
> the Config-files, and maybe some MCA-related fixes, but as things stand
> right now, the fact that I only have a dialup-connection stands between
> me and serious development (<subliminal message>anyone care to sponsor a
> faster connection or hire me?</subliminal message>)
I do agree with that as well. I don't see any reason to worry. It's
open-source, and the codebase will always be available, in *someone's*
repository at least.
>
> Regards: David Weinehall
> _ _
> // David Weinehall <tao@acc.umu.se> /> Northern lights wander \\
> // Maintainer of the v2.0 kernel // Dance across the winter sky //
> \> http://www.acc.umu.se/~tao/ </ Full colour fire </
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
-- Austin Gonyou <austin@digitalroadkill.net> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/