>Supose my fs name is "ext2cryptfs" , will make change in make >files to make a ext2cryptfs.o file and in super.c i gave proper >name in register_filesystem call in function init now , > >here are two cases when it is loaded as module or fixed in kernel >as permenent resident , then in later case where i need to chnage >, from documents i got that i need to change vfs code but wher are >those files > >... > >plz try to solve my trivial question I had a lot of trouble parsing this English, so forgive me if I'm not understanding your question. The term "vfs code" is ambiguous -- people use it to mean different things. But you say you changed super.c in your filesystem driver from what it was in the ext2 filesystem driver that you copied. That is all you need to do. There is no other code you have to change to make your new filesystem type work. But if you are binding your filesystem driver into the base kernel rather than loading it dynamically, there is something you have to do to get the base kernel build to include your code and to get the base kernel initialization code to initialize your filesystem driver. I don't know exactly what that is, though. I've never done it. -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
