On Tue, 15 Jul 2008, Jeff Garzik wrote:No you didn't. You posted a list of problems you have from doing odd and stupid things. Not the reports, not the explanations of what those odd and stupid things actually were in practice, and why they had to be that stupid. Quite frankly, I suspect that it's all a matter of "people compiled their own kernels, and didn't copy the new files, because they just didn't realize they needed to". Which we really don't even need kernel fixes fot, it just needs some education. BUT. If we knew what the details were, we could make the need for education even less, so that it would just work with whatever they do. But yes, if it fundamentally boils down do "you had a script that copied named files by hand", then that script needs fixing. But that's somethign that somebody who compiles his own kernel (especially in an odd environment, apparently) just needs to do. Sometimes build updates need people to fix things. We find gcc bugs, we require people to update. The whole "new kernels should work with old distributions" does not mean that people building the kernels might not have to do _something_ special. Linus --
| Andrew Morton | 2.6.23-rc3-mm1 |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Yinghai Lu | Re: [PATCH RFC] x86: check for and defend against BIOS memory corruption |
| Frederik Deweerdt | [-mm patch] remove tcp header from tcp_v4_check (take #2) |
| David Miller | [GIT]: Networking |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Herbert Xu | Re: [PATCH 2/3][NET_BATCH] net core use batching |
git: | |
