Well, the first writable branch would be IN the initramfs to start
with. Heres how it generally plays out with all the previous aufs
versions in pseudocode:

#INSIDE initramfs:
mkdir "union"
mkdir "rewriteable"

mount -t tmpfs -o size=1024M tmpfs "rewriteable"

mount -t aufs -o nowarn_perm,...,br:rewriteable=rw aufs union

for each external squashfs filesystem:
   mount -o loop filesystem filesystem_dir
   <add branch to aufs>

chroot "union"
switch_root

#finish

Note that all the things happen INSIDE the initramfs, and the first
writeable branch is of tmpfs and the union is of type initramfs.

So now with the new versions, it fails on "mount -t aufs -o
nowarn_perm,...,br:rewriteable=rw aufs union", which I assume is the
newest feature about nfs...sure you can make it work in tmpfs (just
like every previous version) no?

On Wed, Feb 4, 2009 at 12:25 PM,  <sf...@users.sourceforge.net> wrote:
>
> "James .":
>> 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...
>
> Generally you can use aufs in initramfs.
> What is the filesystem type of your first writable branch?
> If it is XFS, then you need to mount tmpfs somewhere and specify xino=
> mount option.
>
>
>> 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..
>
> If you export some kernel functions, then aufs can be an external
> module.
> How do you think about these public GIT trees?
> ----------------------------------------------------------------------
> If I make a public GIT tree and create two branches, is it enough for
> you?
> - branchA
>  equivalent to current aufs2 tarball
> - branchB
>  for building aufs2 as an external module which will be branchA plus
>  some changes
>
> The GIT tree will include whole kernel source tree. Is it OK?
> ----------------------------------------------------------------------
>
>
> 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

Reply via email to