On Tuesday 6 December 2005 6:44 pm, Greg KH wrote:
> > Now what? Do I as a user upgrade my production environment to the latest
> > and greatest kernel experiment, hope that the problems can be fixed
> > quickly, and hope that I don't lose too much data in the process?
>
> No, if you rely on a production environment for your stuff, stick with a
> disto kernel which has been tested and is backed up by a company that
> will maintain it over time.
If the purpose of not having a 2.7 branch or longer RCs is to have people test
the latest vanilla, you can't simultaneously send users away.
I maintain a number of servers and don't like to depend on a distro for the
kernel. I do my tests before deployment and can live with some problems in a
specific release (noone is perfect), but I'd like to have a plan B without
creating my own branch.
Having security patches in a 2.6.(x-1).y would allow me to test the latest
vanilla AND have stable production servers without the rush that usually
accompanies a new release followed by a vulnerability.
--
Bye,
Massimiliano Hofer
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
