[EMAIL PROTECTED] wrote: > Hello Jorgen, > >> Since you didn't seem to understand what I wrote. >> I suggest you one more thing. >> - build your kernel by yourself. >> If you succeed it, then you have a correct environment. > > While I don't know that you are still trying aufs, I have found one > thing about ubuntu edgy kernel. > > The version of this kernel seems to be 2.6.17 basically, but one > interface (at least) is patched by a part of 2.6.18. It is the arguments > of super_block operation umount_begin(). > > Since aufs supports both of 2.6.17 and 18, it uses, > #if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,18) > /* code for linux-2.6.17 and earlier */ > #endif > In ubuntu edgy kernel, this condition didn't work. > Since the LINUX_VERSION_CODE in ubuntu edgy is defineed as 2.6.17, but a > part of code/interface is 2.6.18 actually.
Perhaps I should just compile a vanilla kernel. I hardly have any spectacular hardware on this machine. ;-) > Here is a patch for it. > But I am afraid you may meet another problem which is related to the > kernel interface which is mixed with 2.6.17 and 2.6.18 in ubuntu edgy. Thanks a lot! :-) I had indeed stopped using aufs for the time being, as I needed my system up and running, but now I see why you're developing aufs; for me, unionfs had serious issues with samba-shares and such. :-) I'm now running latest cvs + that patch, and umounting works great! I'll let you know if I stumble into any other problems. ;-) Thanks for your work, appreciate it :-) Kindest regards, Jørgen. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
