On Wed, Nov 19, 2008 at 10:26 PM, Santiago <santi@xxxxxx> wrote: > Hello, > >> >> c. use the model how ext3 and jfs worked together.....writing to ext3 >> >> always entailed writing to jfs journalling. >> >> My earlier statement was wrong.....as I confused jfs with >> journalling....sorry....journalling is done in jbd filesystem in fact. > > No prob. > > I changed jfs to jbd at reading time ;) > > But I'm a bit confused about your statement using fuse. > Well, I have to confess, that I don't really understand what fuse offers, but FUSE just enable you to create any filesystem at userspace.....thus doing away with the need for virtual machine like what you are doing now. A good example is NTFS-3g, which is default in many distro now....which really makes life easier.... > I suppose in userspace I can't read the superblock of other fs or call mapped > kernelfunctions?!? Can...the answer for doing that is in LIBFS.....userspace library to read filesystem..... A good example of multi-fs working together is hostfs + any-filesystem....used in UML....and checkout the implementation...it is really very simple...as a lot of the function fallback to vfs's simplified version of the function......inside fs/hostfs....and the simplified function is in fs/libfs.c (not the same libfs earlier). And hostfs used syscall version of the read/write APIs to read/write to the host FS, eg, pwrite64(), and thus does not make any assumption of the base filesystem it is accessing. Another simple FS is ramfs. -- Regards, Peter Teoh -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
