See, I knew it was something simple. It's just a matter of naming the module exactly the same as what is in the configuration file. Thank you very much. Regards, Brad Johnson On Tue, 2006-03-21 at 11:15 -0500, egoggin@xxxxxxx wrote: > The path selector and hardware handler dm-multipath modules > are loaded using module automatic loading enabled by the > kernel's "CONFIG_KMOD" define. Check out the calls > to request_module from both dm_get_path_selector and > dm_get_hw_handler respectively. > > > -----Original Message----- > > From: dm-devel-bounces@xxxxxxxxxx > > [mailto:dm-devel-bounces@xxxxxxxxxx] On Behalf Of Brad Johnson > > Sent: Tuesday, March 21, 2006 10:41 AM > > To: dm-devel@xxxxxxxxxx > > Subject: path selector question > > > > I am in the process of adding one or more new path selector > > types to the > > device-mapper. While the dm-round-robin module gets > > automatically loaded > > when multipath is started, my new module does not (I have to manually > > add it with modprobe). I know there are many ways I can have this done > > automatically, such as adding my own init script. But I am > > very curious > > how the round-robin module is getting automatically loaded. I have > > grepped through all the source code for multipath-tools and device- > > mapper, as well as the config files for the tools. And while > > it might be > > obvious how this is happening, I can't see it. > > Any help with this will be appreciated. > > > > Thanks, > > Brad Johnson > > > > > > -- > > > > dm-devel@xxxxxxxxxx > > https://www.redhat.com/mailman/listinfo/dm-devel > > > > -- > > dm-devel@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/dm-devel > -- dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
