Message-ID: <3C729C4C.7060903@escriba.com.br>
Date: Tue, 19 Feb 2002 15:41:16 -0300
From: "Alexandre P. Nunes" <alexnunes@escriba.com.br>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020204
MIME-Version: 1.0
To: blesson paul <blessonpaul@msn.com>, linux-kernel@vger.kernel.org
Subject: Re: loading modules
In-Reply-To: <F15LuSbh29cM3oryKFR00012514@hotmail.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org

blesson paul wrote:

> Hi all
> I am a newbie to Kernel world. When I looked into the file system 
> files, I found that the initialization function ( where the file 
> system is registered) is "init_filesystem" where filesystem can be 
> coda, vfat etc. As far as know, the initialization function is
> int init_module(void)
> Then how kernel takes different initialization functions. I want to 
> know whether my know how is wrong or not


you have something like (function parameters supressed for simplifcation):

/* Kernel calls this in your module */
init_module()
{

do_something();
init_filesystem(...);

return whatever;
}


So the entry point for every kind of module, including filesystem 
modules, is init_module(), you don't implement init_filesystem in the 
module, you call it to let the kernel know you want to register a 
filesystem.

>
> Thanking in advance
> regards
> Blesson Paul


Cheers,

Alex

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/