2009/12/10 basile <bas...@opensource.dyc.edu> > You could do it by modifying the ebuild and having it doiwnload the > patch and apply it automatically, but an easier way if you have just one > patch is to do it manually. When the hardened kernel is emerged, its > source is unpacked to /usr/src/linux-2.6.28-r9 with a symbolic link > /usr/src/linux pointing to it. Before compiling, apply the patch > manually there. >
Thanks for your answer... That's what I figured out when I tried. Now I think that it would remind you some experience if I told you that I was thinking about patching hardened-sources with vserver patch... isn't it ? I tried by naively thinking I could just "mash up" vserver-sources & hardened-sources ebuilds but it failed. Looking at some mailing archives, I ended with thinking that's not a good idea, and that applying vserver+grsec official patch to a vanilla kernel would be less painful. Is there any recent story about this combination ? I clearly understand that hardened team won't put vserver patch in hardened-sources. -- Pierre. "Sometimes when I'm talking, my words can't keep up with my thoughts. I wonder why we think faster than we speak. Probably so we can think twice." - Bill Watterson
