>> I used aufs2-standalone from git on April 4 (just before the update on >> April 5 I think) and it works fine with the 2.6.33.2 kernel. My >> instructions for patching are online, but it is just the standard >> instructions supplied with the aufs docs: >> >> http://bkhome.org/sources/kernel-2.6.33.2/ >> username: p#up$py password: lin#u$x (obfuscatd) >> > >Barry, > >For some reason, I can't seem to get the above to work for me. >Has that changed? Or am I just too fat fingered to get it right? >;-)
Do you mean the username and password? Just take out the '#' and '$' characters. On 4/12/10, [email protected] <[email protected]> wrote: > > Phil Miller: >> I managed to build aufs2 now. I edited my PKGBUILD: > > Glad to hear that. > Then I'd ask your opinion. > If I add one line "-include priv.mk" in config.mk and you > prepare the file priv.mk, then your build script will become much > simpler? > It will include priv.mk if it exists. Otherwise ignored. > > For instance, your priv.mk will be such like this. > ---------------------------------------- > CONFIG_AUFS_HNOTIFY = y > CONFIG_AUFS_HINOTIFY = y > ::: > ifeq (${CARCH},x86_64) > CONFIG_AUFS_INO_T_64 = y > fi > ---------------------------------------- > > For linux-2.6.31 and later, AUFS_HFSNOTIFY is recommended instead of > AUFS_HINOTIFY. Since INOTIFY is listed in > Documentation/feature-removal-schedule.txt. > See the aufs manual in detail. > > > J. R. Okajima > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev
