"Aaron M. Ucko" <[email protected]> writes: > Hi, Russ!
> The 2.6.38-1 kernel packages that recently hit unstable disable the > infamous big kernel lock, on which OpenAFS 1.4.x evidently still > relies; my build failed with > /usr/src/modass/usr_src/modules/openafs/src/libafs/MODLOAD-2.6.38-1-amd64-MP/osi_groups.c:393: > error: implicit declaration of function ‘lock_kernel’ > /usr/src/modass/usr_src/modules/openafs/src/libafs/MODLOAD-2.6.38-1-amd64-MP/osi_groups.c:396: > error: implicit declaration of function ‘unlock_kernel’ > and grep revealed a lot of other references to (un)lock_kernel. :-/ Hm, that's interesting. The version currently in unstable pulls up the changes in Ubuntu so that it would build with 2.6.38 in Ubuntu, and those apparently worked fine. I wonder what's different. > Under the circumstances, I'm inclined to suggest going ahead and > uploading the latest 1.6.0 release candidate to unstable. (FTR, > 1.6.0~pre2-1 built successfully, though I have yet to try actually > running it.) Yeah, it looks like the global kernel lock code was removed from the 1.6 branch a long time ago. We're hopefully fairly close to a 1.6 final, and some major bugs are still being fixed, so I'd rather wait for upstream to bless 1.6 before uploading it to unstable. But I probably don't have much time left, given that 2.6.38 is now in unstable. I was hoping that the Ubuntu patches would tide us over.... -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
