On Tue, Jun 23, 2009 at 10:09:22PM +0200, Sven Joachim wrote: > On 2009-06-23 21:30 +0200, lee wrote: > > > On Tue, Jun 23, 2009 at 01:44:21PM -0500, Kumar Appaiah wrote: > >> > >> I believe that the patch-2.6.29.x applies against the tree of 2.6.29, > >> which is why some hunks would already be present if you try to apply > >> it against 2.6.29.4. > >> > >> The easiest solution is to get the full 2.6.29.5 tree, or get the > >> 2.6.29 tarball and then apply this patch. Someone correct me if I am > >> wrong. > > > > My understanding is that patch-2.6.29.5 is supposed to patch (the full > > source tree of) 2.6.29.4 to kernel version 2.6.29.5, the idea being > > that it saves you from having to download the current full source > > tree. Isn't that so? > > No, it is as Kumar said. And you don't have to download the full source > if you have 2.6.29 already.
Aha! Then this is the problem, I don't have 2.6.x, only a Debian kernel 2.6.24 and a standard kernel 2.6.29.4. So I would have to download 2.6.29 and then apply the patch-2.6.30? I'll try that; I don't mind downloading, only starting from scratch with a new configuration so shortly after I switched to 2.6.29.4. I'll apply 2.6.30 and use make oldconfig and see what happens ... > With your proposal, you would need 2.6.29, _every_ patch-2.6.29.y > and apply them consecutively -- this becomes rather tedious if y is > large. With the way I was thinking it works, you would already have a 2.6.29 or a 2.6.29.x kernel and then apply one patch after another to get to the .x you want. Like in my case, I would start with the 2.6.29.4 I already have and apply 2.6.29.5 and 2.6.30: only two patches. How many patches you would have to apply would only depend on how large the gap is --- and if it was a large gap like from 2.6.24 to 2.6.30, I'd download the full 2.6.30 anyway and it won't matter. > > If I need to download the full source again, I'd > > download 2.6.30 and won't need to patch anything. > > I always download linux-2.6.x.tar.bz2 and patch-2.6.x.y.bz2. That seems to be the better way since I could keep applying the patches from there ... > Actually, "make oldconfig" is the best you can do to check every new > kernel option. It takes a bit of time if going from 2.6.x to 2.6.x+1, > but for most questions asked you can just press Enter. Ok, let's hope it works just fine :) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
