Hi
hi
Thanx
for reply..
i'm searching for the vfs file wher i need to give the instruction for registraring file system, but i didn't got the code file, so i thought that it will auto matically do it in the kernel.
but when i tried to load it as module, it gave versionoing problems and load failed
waiting for reply
Quoted 17 lines · On Wed, 19 Feb 2003 Bryan Henderson wrote :
Quoted 5 lines
i've copied the ext2 file system code, and changed its name
in
Quoted 1 line
init function but when i try to mount some fs with the new name
it
Quoted 1 line
is saying that it is not supporting,
You didn't mention loading the filesystem driver. You did, didn't you? Any error messages (kernel messages) issued?
Before bringing mount into the picture, look at
/proc/filesystems. If your new filesystem type name doesn't show up in the list, you're already broken.
Quoted 9 lines
--
Bryan Henderson IBM Almaden Research Center
San Jose CA Filesystems--
Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
R@j@r@m
Quoted 6 lines
but when I tried to load it as a module, it gave versioning problems and the load failed
Versioning problems are common. It means you didn't use the same kernel headers to compile the module as were used to compile the base kernel into which you are trying to insert it.
It can be tricky to get your compile straightened out, and it has nothing to do with filesystems, so I don't want to go into it on the linux-fsdevel list (which I am copying just so others on that list can see that there was a response).
I can tell you this, though, which you can use when you get your module to
load: The ext2 filesystem driver registers itself as a driver for the "ext2" filesystem type by calling register_filesystem(), which it does in the source file fs/ext2/super.c, in a function that gets called as the module loads. If you did not change that file in your copy, your module will try to register itself as a driver for "ext2" and will fail because there is already a driver for "ext2". You will need to make up a new filesystem type name.