Karsten Gebbert: > I have repeated the entire process of patching and building and=20 > eliminated some factors that could have contributed to the segfaulting I=20 > described in my earlier mails, so now I can get the rt- and aufs-patched=20 > kernel to boot in both systems, regular Debian install _and_ new=20 > snapshot liveCD. So far, everything looks great! For now I have enabled=20 > debugging symbols for aufs and the kernel so it might become easier to=20 > trace any problems from here. Thank you so much for your support on this=20 > issue!
Glad to hear that. Disabling CONFIG_AUFS_DEBUG makes aufs uncleanly compiled. Here is a patch for that. If you apply this patch, aufs should be compiled cleanly and work well without enabling CONFIG_AUFS_DEBUG (as you did previously). But please test rt-aufs well since I don't know what test is good enough for that. > One question that I'd like to ask you is how this could possibly work in=20 > the future for newer kernel releases. Would it be possible to create a=20 > branch for this patch so that its officially available for future=20 > releases? What would you suggest in that respect? aufs2-rt13-29.3.patch (yes, I named it just now) highly depends upon both of the kernel and RT patch version. And I don't think it is a good idea to create a branch such like aufs2-29.3-rt13. Additionally aufs2 GIT trees are based upon linux-2.6.git which does NOT contain v2.6.29.3. The linux-2.6.git contains only the first version of every kernel release. The GIT tree which contains v2.6.nn.X is linux-2.6-stable.git. Finally I am going to create aufs2-rt13-29.3.patch file in aufs2-standalone.git#aufs2-29 branch only. How do you think? J. R. Okajima ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects
