Messages in this thread | | | From | John Stoffel <> | Date | Thu, 6 Dec 2001 11:59:50 -0500 | Subject | Re: [kbuild-devel] Converting the 2.5 kernel to kbuild 2.5 |
| |
Rik> IMHO it's not acceptable that people upgrading from one 2.4 Rik> kernel to the next will have to install Python 2 on their Rik> machine.
So has anyone had time to test the Python version 1.5 based CML2 that was posted? Would that make it more acceptable?
Rik> Security bugs are and will be discovered, you cannot make it Rik> impossible for people to do security upgrades.
This is a bogus arguement, since I could say the same about installing new kernels. There could (and will) be security problems with the kernel, so we should not release new ones until we have proved they are correct.
Yeah, I'm being a pain here, but Rik is making a bad arguement here.
Rik> Yes, I agree the method you're using to smuggle CML2 into a Rik> stable kernel is insidious. Please stop it.
I think you're being too harsh here. Smuggling is not happening here, it's been very aboveboard that CML2 might (I repeat MIGHT) be back-ported to the 2.4 series of kernels. But since it would happen in the -pre tree, there would be plenty of notice. And people could complain then.
The requirement for python2 is a bit of a pain, but hey, for 2.5, it's not a problem.
John John Stoffel - Senior Unix Systems Administrator - Lucent Technologies stoffel@lucent.com - http://www.lucent.com - 978-952-7548 - 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/
| |