Thanks for that. This is what I feared...I use aufs as a initramfs before the actual boot, to create a live-cd like structure, and Im sure im not the only one that does this (look at slax etc). I think it should definetely support initramfs (im not sure if this is the same as ramfs, but it sounds like it), despite not being exportable by nfs...
This is another reason why I implore you to make a cut down, nfs-less version as well as a nfs version of aufs, or otherwise continue doing cvs updates where you can select the options you can compile into the module. Looks like ill have to hack some code. Wish me luck.. On Tue, Feb 3, 2009 at 9:38 PM, <sf...@users.sourceforge.net> wrote: > > "James .": >> Finally I got home and tried some things, it seems that this version >> of aufs does not like rootfs?? >> >> Heres the error: >> aufs au_xino_def:1114:mount[420]: xino doesn't support >> /tmp/.aufs/.xino(rootfs) >> >> I thought the xino file was in the first rw branch, why is it now >> /tmp/.aufs/.xino? >> >> However, it is interesting that a SECOND invocation of the command >> line ( mount -t aufs -o nowarn_perm,noplink,udba=none,br:/folder=rw >> aufs union ) causes a different error: >> aufs test_add:208:mount[431] unsupported filesystem, /folder > > I had to describe more about the difference from aufs1. Sorry for your > unconvienience. > > For xino files, aufs1 finds the first writable branch, if it is NFS then > try /tmp. If /tmp is NFS too, then produces a warnining and returns an > error. In aufs2, not only NFS but also all remote fs, XFS, aufs, > ecryptfs and fs which doesn't support NFS-exporting. > Your first writable branch is any of them? > (See au_test_fs_bad_xino() in fs/aufs/fstype.h) > > For your second case, aufs2 rejects the filesystem of branhces, procfs, > sysfs, configfs, ramfs and aufs. Is your folder any of them? > (See au_test_fs_unsuppoted() in fs/aufs/fstype.h) > > > J. R. Okajima > ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
