Thanks One last question : it the source of this patched kernel open ? Thanks Maurice On Fri, May 2, 2014 at 8:28 PM, Corey Minyard <cminyard@xxxxxxxxxx> wrote: > On 05/02/2014 02:40 AM, Mau Z wrote: >> Thanks >> >> The answer is very surprising. >> I would assume that more than one person would have such an experience. > > Well, the LTSI organization may have done it. That's all I can think > of, though. > >> >> >> I am curious regarding the magnitude of work to be done. I am >> especially intersted what happens when you have to handle another >> Linux version for your distribution. >> >> Is this job done just once (for one specific Linux version) ? > > Once for a specific Linux version, 3.10. > >> or >> You do the job once, and then do the same fixes on the other Linux >> version (more or less) ? >> or >> You have to do the same job all over again in every linux version ? > > We will on the next version we release, yes. > >> >> >> Is the following discription correct ? >> Basically the job is >> 1) Download kernel >> 2) apply RT-patch >> 3) apply PAX patch >> 4) compile and fix warnings and errors > > Well, there's testing :). But basically yes. Resolving the conflicts > is the biggest deal, really, in the above process. And testing is a lot > bigger than that :). > > We integrate a lot of other things, so it's hard to remember the > specific RT/PaX issues. > > -corey > >> >> Thanks >> again >> zmau >> >> >> On Thu, May 1, 2014 at 2:53 AM, Corey Minyard <cminyard@xxxxxxxxxx> wrote: >>> On 04/30/2014 05:47 PM, Mau Z wrote: >>>> I have some more questions concerning the relation between PAX and the >>>> RT-Patch : >>>> A) Can they work together ? >>> It can be made to work. We have it working together in our distribution. >>> >>>> B) Do you know if it matters which patch is applied first ? >>> Not really. >>> >>>> C) Is there any documentation about this subject ? >>> None that I know of. I imagine that I'm the only person who has ever >>> done this. >>> >>> There are some conflicts (a few are non-trivial, but not excessively >>> complicated, IIRC). But it's not something insurmountable. You do have >>> to have a fairly good understanding of kernel code. >>> >>> -corey >>> >>>> >>>> Thanks >>>> zmau >>>> -- >>>> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in >>>> the body of a message to majordomo@xxxxxxxxxxxxxxx >>>> More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
