Hi Mike, I'm confused. In fact, I use a cpio archive. I've tried to print the au_test result when execute "au_test_fs_unsuppoted" by aufs. When I boot into the busybox, I mount the aufs manually, it is said "unsupported file system" and give the 1 when do au_test_ramfs. So I use the initramfs, but it is also ramfs, right? Anyway, thanks for the knowledge between initramfs and ramfs. I will have a deeply research for it. TualatriX
On Wed, Mar 11, 2009 at 10:40 PM, Michael S. Zick <[1][email protected]> wrote: On Wed March 11 2009, TualatriX wrote: > Hello J. R. Okajima: > > Thanks for your reply! > > Just as you said, my use-case is mounting file system in initramfs. Without > ramfs support I can't mount file system when booting in initramfs. > > I'm thinking whether it is possible to make aufs2 support ramfs again. > > And I've read the history, it seems that aufs1 got temporary support for > linux-2.6.28. So if aufs2 can't support ramfs mount, I will look back to the > aufs1 and try it. > > Anyway, Thank you very much! > > TualatriX > > On Wed, Mar 11, 2009 at 9:24 PM, <[2][email protected]> wrote: > > > > > Hello TualatriX, > > > > TualatriX: > > > After upgrade to the Linux 2.6.27, I start to use aufs2, but I it seems > > that > > > aufs2 doesn't support mount ramfs and aufs self. > > > > Yes. > > > > > > > Aufs2 doesn't support mount ramfs and aufs, the comment says mount aufs > > will > > > be supported in next version. > > > So I want to know if there's possible to support mount ramfs. The aufs1 > > > works well with ramfs. I need this feature. > > Are you sure? You are writing about two different things: ramFS :: an area of main memory and initramFS :: built in the VFS buffers not in main memory. The difference between initramFS and tmpFS (both built in the VFS buffers) is that initramFS does not have any backing store; tmpFS uses swap for its backing store. How to tell what you are using: If what you are loading is a gzip'd, cpio archive - your using initramFS If what you are loading is a file system image - your using ramFS (the initRD style) If you are using a gzip'd, cpio archive - you can disable "ramFS" in your kernel and everything will just keep on working. ;) (your not using it). In either case, you can substitute the tmpFS device and system by changing your init scripting in the memory image or file system image you are loading. Much, much, easier than re-coding auFS. ;) Mike > > In technically, ramfs and readonly aufs can be a branch of aufs. > > Actually aufs1 supported them, as you wrote. > > > > A readonly aufs branch requires CONFIG_AUFS_ROBR and it was dropped from > > aufs2, because I think there is no user of it. > > > > A ramfs is transitting tmpfs and the only use-case of ramfs left is > > rootfs, I am afraid. Please try replacing ramfs by tmpfs, if you can. > > > > > > J. R. Okajima > > > -------------------------------------------------------------------------- ---- Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. [3]http://p.sf.net/sfu/www-adobe-com References 1. mailto:[email protected] 2. mailto:[email protected] 3. http://p.sf.net/sfu/www-adobe-com
------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
