Messages in this thread | | | Date | Thu, 16 Dec 1999 07:51:41 +0100 (MET) | From | David Weinehall <> | Subject | Re: [security] Big problem on 2.0.x? (fwd) |
| |
On Wed, 15 Dec 1999, Rogier Wolff wrote:
> Alan Cox wrote: > > > But there are lot of people (mainly companies) that either won't update > > > until they have finished evaluating v2.2.xx (somewhere around when we > > > release v2.4.5 and v2.2.25 or so...), and others that have custom-made > > > drivers that haven't been forward ported to v2.2.xx yet. > > > > Yep. Minimise changes though. > > Example: I maintain a system that will be on 2.0.x until 2009. It uses > 5 custom kernel-drivers.
I gather this system works pretty well then...
> (It's getting an upgrade from 2.0.20 to 2.0.37 in the first quarter of > 2000!)
I do _REALLY_ recommend that you wait for v2.0.39, or at least install v2.0.38 plus the ip_header fix (that'd be similar to the v2.0.39pre1 patch that I'm about to drop on Alan soon)
/David _ _ // David Weinehall <tao@acc.umu.se> /> Northern lights wander \\ // Project MCA Linux hacker // 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.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |